use uuids for input schemes [SYNTH-251] - #1423
Conversation
5ad6157 to
761dd26
Compare
8accae3 to
c577724
Compare
|
no idea why the tests are failing, doesn't seem related to this pr |
04397c9 to
82e480a
Compare
rutmanz
left a comment
There was a problem hiding this comment.
The main purpose of this ticket was to fix the react state problems around how input schemes are referenced (the same ones you identified in your review of #1425). Now that we have unique IDs, the state can be the ID and then keep the scheme objects themselves isolated to the InputSchemeManager
| }) | ||
|
|
||
| return allSchemes | ||
| return [...this.customInputSchemes, ...this.defaultInputSchemes] |
There was a problem hiding this comment.
Yeah I asked azalea about that and she said not filtering out default schemes with the same name was a good idea, but I can revert that change.
6255fc0 to
fc7fc88
Compare
|
@rutmanz soz about force pushing, I just wanted to make sure I merged correctly and I find that rebasing makes that a lot easier. @Dhruv-0-Arora would be great if you could review this. |

Task
SYNTH-251
Symptom
Solution
Verification
Before merging, ensure the following criteria are met: