...
- Add two (2) new HTML template files, cloning and editing from similar files
- main record page (in defaults/html/pages)
- advanced search page (in defaults/html/components)
- Add two (2) new JSON config files in the UI's defaults/config folder, cloning and editing from similar files
- main record page (...json)
- secondary tab page (...-tab.json) (this config file is needed for a new procedure, but not for a new authority record type)
- Add text labels relevant to the new procedure to the default message bundle file, defaults/bundle/core-messages.properties
Fetch the UISpec In addition, for authorities, need to edit js/Demands.js
per Yura, at some point you won't need to do that, app layer might be able to generate this for the UI
When working on the additions above, fetch the UISpec by making a call to the app layer, after doing app layer config, in order to make editing the HTML templates and message bundle easier. This will show you:
- Selector names needed in the HTML templatetemplates
- Message label keys needed for bundle
Finally, fetch the UISpec and UISchema by making calls to the app layer, and place those into src/test/uispecs and src/test/uischema. Those static JSON files are used for local testing of the UI layer.
Message bundle overlay - could this be per-tenant for contributions?
App layer might be able to read all files in bundle folder
App layer merges all overlay files just once
- App layer init doesn't rebuild that - it could be added
Create advanced search form template for your new procedure
...
Boolean fields
In UI, would add checkbox
Test cases added to ensure that's working
test/js/RendererTest.js
...