Repository navigation
Preserve study plan context on submissions - #3
Open
SpideyPotter wants to merge 1 commit into
Open
SpideyPotter wants to merge 1 commit into
SpideyPotter wants to merge 1 commit into
Conversation
This branch has not been deployed
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.
Accepted TUI submissions could appear in LeetCode history while the official study plan still showed the problem as incomplete. A browser capture showed that LeetCode sends
study_plan_slugin the submission JSON and includes the plan context in the problem-page Referer.This change passes the selected plan slug through the TUI and sends it in both places. The submit endpoint and regular request shape stay the same. Regression tests cover both plan and regular submissions.
The reporter confirmed the patched binary advances official Top Interview 150 progress. Submission regression tests passed. Full local suite verification was limited by Node runtime failures in the JS/TS runner tests and a timeout in the TUI test harness.