feat: resolves issue #16 - add loading state while routes are calculated - #64
Merged
Conversation
… are calculated
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
2 participants
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
Resolves #16 — adds a loading state while routes are being calculated, ready to be styled ahead of Phase 2's real network calls.
Changes
src/App.jsx:handleSubmitis now async with a 500ms artificial delay before computing routes. While loading, results are replaced with a "Finding routes…" indicator (role="status"); the submit handler also guards against duplicate submissions.src/styles.css:.loading+.spinnerstyles (CSS keyframe spin).tests/App.test.jsx: verifies the loading indicator appears on submit and disappears once results are ready.CHANGELOG.md: entry under Unreleased.Verification
npm testpasses (24/24 across 5 files).npm run buildpasses.