Hubs-Foundation / Hubs-Foundation/Spoke
Spoke auto-regenerates FloorPlan unexpectedly causing lost work
- Dominant language
- JavaScript
- Stars
- 679
- Forks
- 260
- PR merge metrics
- No merged PRs in 30d
Description
When using the FloorPlan, the settings are complicated enough that it's common to want to test out settings and re-publish the scene before committing to those changes. However, because the FloorPlan auto-generates (and saves) when hitting 'Publish', the user has no idea that it happened. Then they're in a situation where they may have changed a few parameters, but first thought, "Wait--let me publish first to see how it's working before I regenerate this FloorPlan..." but it has actually already taken the current unsaved settings, published with them, and also saved over their old settings. This can cause a confusing loop of changing parameters that you think you haven't tried yet.
Contributor guide
Research direction
The issue names no file, test, or entry point. Start by reproducing the FloorPlan workflow: change settings, publish without regenerating, and verify whether the current settings are saved or applied unexpectedly. Done means publishing no longer silently regenerates and saves the FloorPlan, while the intended settings workflow remains clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100