Verified interview challenge
Build a recipe manager with version history
Extend a recipe service from basic operations to controlled edits and recoverable history.
Unlock with Full AccessThe challenge
A recipe service grows from creating and searching records into user-controlled edits and version history. Your implementation carries forward as each level introduces more relationships between recipes, users and past changes.
Keep the current recipe useful for search while preserving earlier versions and the specified edit permissions. The challenge rewards a data model that can support new behaviour without quietly changing what earlier operations mean.
What you'll practise
Search and identity
Keep stored records and ordering correct as the service adds queries and users.
Version history
Preserve earlier states while supporting new edits and rollback.
# Build on your implementation
# Run checks for the current part
# Full starter code includedRun your code to see results.