In edit mode, it would be nice if RapiD remembers my data settings (e.g. disabling features) between tasks
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start by tracing the quick edit flow where RapiD is activated and where data-feature defaults are initialized when a new task starts. Check how task transitions handle those settings; done means user-disabled data types persist between tasks in the same challenge.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Depending on the task you're working on, sometimes it's optimal to disable certain types of data from OSM. For example, if you're challenge is working exclusively about highways, maybe disabling points, buildings or water features are useful.
Describe the solution you'd like
In these cases, when I use the quick edit option rather than using JOSM, I would normally disable certain data features from iD/RapiD, but currently, when I start a new task, RapiD doesn't remember what I disabled last time. Probably because Rapid is activated with hard-coded defaults, rather than trying to remember how I used it last time I did the same task?
Describe alternatives you've considered
Disabling the data types between tasks in the same challenge is tiresome.
Additional context
Data features in iD/RapiD may be enabled/disabled by a user:
- Dominant language
- JavaScript
- Stars
- 167
- Forks
- 39
- Avg merge
- 22h 29m
- Merged PRs (30d)
- 8
Getting set up
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.
More from maproulette/maproulette-frontend
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
maproulette/maproulette-frontend#2923 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 52/100
maproulette/maproulette-frontend#2922 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 30/100
maproulette/maproulette-frontend#2909 · 3 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
maproulette/maproulette-frontend#2900 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
maproulette/maproulette-frontend#2896 · 4 comments ·
Maintainers usually reply within 1 day
All issues in maproulette/maproulette-frontend
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
githubnext/gh-aw-workshop#3897 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
agent/quality hive/hosted-available-lke648397-260827-5n31 quality testing
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
Maintainers usually reply within 1 day