Fix: #123- The solution schema should appear in a saperate "Solution" tab after clicking "View Solution"#199
Open
Me-Priyank wants to merge 3 commits intojson-schema-org:mainfrom
Open
Conversation
…r the tour page UI." This reverts commit 1910a58.
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
1 participant
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.
What kind of change does this PR introduce?
Feature, UX Improvement, and Bugfix
Issue Number:
Screenshots/videos:
View_solution.mp4
If relevant, did you update the documentation?
No
Summary
When a user clicks the "View Solution" button in a lesson, the correct solution schema immediately replaces the user's current code in the editor. This overwrites the user's work, making it impossible for them to compare their faulty logic side-by-side with the correct solution to understand their mistakes. This severely hampers the learning process.
Does this PR introduce a breaking change?
No