-
Notifications
You must be signed in to change notification settings - Fork 60
Support Fields Having Pre Select Scoring Zones [AARD-1894]
#1211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Fields Having Pre Select Scoring Zones [AARD-1894]
#1211
Conversation
[AARD-1894]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm trying to test this but it doesn't actually seem to persist the changes? These are the steps I'm taking:
- Import field
- Add scoring zone
- Go to devtool editor and click "save" (I see the toast that says they've been persisted)
- Clear preferences (because scoring zone data is already scored here; I think part of this PR would also be ending the storage of scoring zones in the preferences cache so it can stay with the mirabuf file)
- Reload
- Import same field
- No scoring zones are present
I'm not seeing any console errors
Wouldn't saving data back to the mira file require us to store the mira files for each individual users? The way I understood the PR (I might be wrong) the goal was to allow fields to come with pre-selected scoring zones. Meaning that in the exporter a new tab would be added saving this data to the mira file, that way when the user comes and tries to load a field all the scoring zones are already pre-configured. |
Ah I didn't incorporate the "clear preferences" step on my interpretation of the caching deliverable of this ticket. The changes do persist after reloading if the preferences aren't cleared. However, I don't think it makes sense for the changes to still persist after preferences are cleared especially for default fields. I think your suggestion in |
As the current behavior on |
The issues should all be addressed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it looks like you didn't update the type for DevtoolMiraData (it's still unknown), but other than that looks good
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well done getting the integration of everything all lined up. Nice work.
* dev: (90 commits) Delete `disableClickAway` + formatting Update modal clickaway logic Race condition removed code cleanup and formatting feat: adding export of tags into assembly data isort formatting Scores Reset on Match Completed Disable Default Key Functions formatting feat: added blank icon to allow users to select rows fix(snyk): update version requirements globalAddToast Chaining Removed Default Configs in Typescript File reorder dependencies chore(installer): update python packages to avoid vulerabilities fix: cleaning dead code and fixing spelling error Unused Imports Removed Merge Fix fix: clean up workflow spacing, use latest checkout and setup-node steps fix: use correct package.json path ...
Partial requested changes made. Remaining issues can be addressed at a later date but not worth delaying PR for said changes.
Task
Allow users to choose and cache/export where scoring zones are positioned.
AARD-1894
Symptom
Benefits of having direct user editing: bulk edits and reuse, version control and diffs, schema validation
Solution
Developer Tool
.UserData
and import them for use cases such as cleared cacheVerification
FieldMiraEditor.test.ts
and all passedScoringZonePreferences
are loaded after refresh