Repository navigation
Owned properties and upgrades: Settings panel, Businesses tab with gear - #27
Merged
Merged
Conversation
…l, Businesses gear - src/data/properties.ts: property catalog with toggle and choice upgrades (empty; trackers add entries) - src/lib/properties.ts: owned/upgrade logic and parsing, with tests - State version 3 adds `properties`, migrated from version 2 with a stored sample - Settings lists every property; the Businesses tab shows owned ones with a gear to edit them - Kit previews both with sample entries; decision 011 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Deploying lsos with
|
| Latest commit: |
c2910f9
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://3962da04.lsos-2qs.pages.dev |
| Branch Preview URL: | https://claude-5-owned-properties.lsos-2qs.pages.dev |
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.
What this does
Adds the mechanism for telling LSOS which properties you own and which upgrades you bought. A property catalog lives in
src/data/properties.ts, with two kinds of upgrade:toggle(e.g. equipment/staff) andchoice(e.g. a nightclub technician's assignment). The catalog starts empty, because each tracker issue adds its own sourced entry. Owned settings are saved in state version 3, which includes a migration from v2 and a test with a stored sample. Settings gets a Properties panel. The Businesses tab shows only owned properties, each with a gear that opens its settings in place. Design is in decision 011.Closes #5
How to check it
npm run dev, open#/kit: under "Properties", tick/untick owned, toggle the upgrade, pick a worker option. "Businesses tab" below lists only owned samples; the gear opens the same settings, and when it's closed the panel shows a summary of the upgrades.Checklist
npm run verifypasses🤖 Generated with Claude Code
Generated by Claude Code