Repository navigation
feat(metadata): declare a challenge's difficulty in problem.md - #62
Merged
Merged
Conversation
A top-level `- Difficulty:` line takes easy, medium or hard, case-insensitive, and is stored lower-cased. Any other value fails the load. It is reported as `difficulty` in challenge metadata, including the schema state the platform syncs from, and is omitted when a challenge declares none, so a consumer can tell "not declared" from a level and keep what it already holds. Existing databases gain challenges.difficulty in place, defaulting to ''. A difficulty change is metadata-only and refreshes without a rebuild.
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.
A top-level
- Difficulty:line takes easy, medium or hard, case-insensitive, and is stored lower-cased. Any other value fails the load. It is reported asdifficultyin challenge metadata, including the schema state the platform syncs from, and is omitted when a challenge declares none, so a consumer can tell "not declared" from a level and keep what it already holds.Existing databases gain challenges.difficulty in place, defaulting to ''. A difficulty change is metadata-only and refreshes without a rebuild.