Auto-save, read only option for projects, plus quick spawn sandbox
Open
Nobody has claimed this yet.
Collab Editor
Epic
sandboxes and sync
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
As a user with a sensitive production project, I'd like to:
- prevent editing for an entire env (when
prod, all workflows are read only) - have a "switch sandbox" or "create sandbox" button clearly accessible from the Canvas & IDE so that I can make edits when I think of them
- Have a "merge" button clearly accessible from the Canvas & IDE so I can "publish/deploy" back to my sensitive read-only env.
- In all NON-protected envs (i.e., in all editable ENVs!!!) we should auto-save changes to workflows
🤯
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
Start by tracing the Canvas and IDE workflow-editing entry points and how environments are represented. Define the protected read-only behavior, sandbox creation or switching, merge actions, and auto-save for editable environments. Done means all four requested capabilities work consistently across the Canvas and IDE.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100