Feature Request: Project files support (save/load settings and edit history)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 278
- Forks
- 31
- Avg merge
- 13h 32m
- Merged PRs (30d)
- 4
Description
Hi!
I think adding support for project files would be incredibly handy. It would allow users to save and load their current image along with all applied settings. Beyond user convenience, this would be a huge help for debugging and troubleshooting, as users could simply attach a project file to an issue to easily reproduce bugs.
Another great feature tied to this would be saving the edit history directly into the project file. This way, users could seamlessly undo/redo changes even after closing and reopening Kromacut.
I would be more than happy to work on this and submit a Pull Request if you think it would be a valuable addition to the project. Let me know your thoughts!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files, tests, or an entry point. Start by mapping how Kromacut currently stores the image, settings, and edit history, then clarify the project-file format and persistence scope with maintainers. Done means users can save and reopen the image and settings, with edit history available for undo and redo after reopening.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, tauri, typescript
- Domain
- desktop, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100