Feat/http validator and links#62
Merged
Merged
Conversation
… use inbound target rules
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of Changes
This PR introduces HTTP web server verification in the learning validation engine and improves the Roadmap UI with dynamic access links, markdown formatting, and copy buttons.
Key additions:
http_get_containsValidator: Adds a backend learning engine validator that executes localizedcurlrequests inside docker containers to verify page content (e.g. database rows rendered in HTML).example-first-architectureroadmap instructing learners to build and start a Python web server connected to the PostgreSQL database, and open port 80.http://localhost:<mapped_port>link under step instructions if the target container is running, placed in a public subnet, and has port 80 allowed inbound.userstable via the database explorer inspector rather than simply instructing them to write SQL.ALLOW ALLoutbound) from leaking into ingress checks.Types of Changes
Verification & Testing
Automated Checks
npm run lintsuccessfully with no errorsnpm run buildsuccessfully with no compilation errorsnpm testsuccessfully (all tests pass)Manual Verification
httpGetContains.test.ts(passed).npm run roadmap:validate) againstexample-first-architecture.jsonto verify schema validation (passed).LearningPanel.test.tsx,useLearningPlayer.test.ts,useRoadmaps.test.ts) to verify component behavior, styling fallbacks, and navigation logic (all 21 passed).Checklist