d8897133f7
* typeahead feature changes * updating * fixing test * fixing interaction testd * fixing pipeline failure * clang error * resolving comments * resolving feedback * fixing test cases * clang fix * clang fix * fixing Ui tests * fixing uitests * keyboard fix * fixing clang errors * clean up * adding design document --------- Co-authored-by: Jyoti Kukreja <jyotikukreja@Jyotis-MacBook-Pro.local> |
||
|---|---|---|
| .. | ||
| DesignDiscussions | ||
| assets | ||
| devops | ||
| elements | ||
| features | ||
| HostConfig.md | ||
| README.md | ||
| RendererStatuses.json | ||
| RendererStatuses.md | ||
| SpecTemplate.md | ||
README.md
Specs
If you are looking to write a spec for your feature please make sure to reference our contribution guidelines and spec template
Updating specs
Setup
For the best experience...
- Install Node.js
- Use Visual Studio Code
- Install the Run on Save extension by pucelle
- Make sure you install the right one, there's many under the same name, check the author's name
- If it fails to install, update your version of Visual Studio Code
Updating the property table
The property table in the spec documents is auto-generated. Do NOT hand-edit it, as your changes will be lost!
Instead, open schemas\src and update the schema. If you followed the instructions in Setup, after you save your changes to the schema, the specs will be auto-updated in about 10 seconds.
Re-naming an element
If you're re-naming an element type (not just a property, but an element that has its own spec file), here's the best way to do so (so that your changes are tracked as an update rather than delete and re-create).
- Rename the file in
specs\elements - Then, update the
schemas\src
This will ensure that the updates to the schema will be written to the existing spec, rather than creating a new spec file (and leaving an untracked file that doesn't auto-delete).