Repository navigation
Bump to v3 - #88
Merged
Merged
Bump to v3#88
Conversation
|
This is magical. Is there anything you didn't check in? How do you get "version: 3"? |
Member
Author
|
It's a draft PR so this is just the updated fixtures. I still need to update |
BNAndras
marked this pull request as ready for review
October 13, 2026 04:44
IsaacG
approved these changes
Oct 13, 2026
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
3 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.
Closes #19. I'm using the JavaScript track approach with an opt-in custom flag in the exercise's config.json. Each top-level describe gets numbered sequentially in order of appearance at runtime, and each test inherits the task id of the top-level describe it falls under.