Don't erase custom dataclip when switching between input pickers
Open
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
When typing a custom input in the new input picker, if you switch to view either "empty" or "existing" when you navigate back to your "custom" input, the text is gone.
These are views, you haven't "done anything" yet, and we should ensure that the custom input isn't erased while you're looking around.
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 reproducing the behavior in the new input picker: enter custom input, switch to the "empty" or "existing" view, then return to "custom". Trace how the picker handles these view changes and ensure the typed custom input remains available when navigating between views.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100