Label keys should be specific to their context. This allows having
different labels for the same thing in different contexts (e.g.,
having different headings for the tea title in the regular list view
and the FE editor).
We take the plugin as the context here, which allows us to reuse labels
between different actions of the same plugin (e.g., between the list view
and single view).
This is a pre-patch for adding a CRUD plugin for tea records.
This property contains only the UID of the owner FE user, but not
a relation to a FE user model. This is because we neither have nor
need a FE user model for the purposes of the CRUD plugin.
- Move npm tools and config to default places
- Remove now unnecessary config file parameter from npm scripts
- editorconfig and eslint config contradict, adapt editorconfig
- switch JS indent linting to TYPO3 coding standard of 2 spaces
- adapt composer scripts for new npm location
This now matches what the TYPO3 Core uses.
We still use the XLIFF 1.2 schema for validation as version 1.2
is the first fully ratified version.
Closes#198
