Currently trying to see how the JSON schema would look like by writing it hand before attempting to then write a script to help write the same JSON to a file by looping over types
- fixes padding-top on property layout for all but first item
- fixes whitespace below workspace layout element
- fixes cotent tab background color
- sets first content tab to active on load
* new api models
* use new PackageResource
* do not error out on missing default exports (esmodules auto-execute)
* do not check for js extensions (they might have been registered on the client without a js file)
* prepend the api baseurl to any relataive server JS dependencies
* ignore tsbuildinfo
* create base file for tsconfig
* extend from base config and optimise include/exclude paths
* install rollup plugin to handle json files
* use plugin to bundle json files
* call script for cms builds that builds libs
* add rollup config to utils lib
* add a context token to the extension registry instance itself and provide it through BackofficeElement
* add rollup node resolve
* add node resolve
* only include element mixin in element library
* add error description to module load error
* add types to UmbExtensionRegistry token
* set UmbNotificationService as string in its token to avoid minification
* correct comment
* reverse order of checks
* add host to server extensions and support life-cycle check
* add imports
* use lit rather than lit-html
* correct comment
* add PackageManifestModel
* add import
* run libs build for cms
* revert reorder
* use string name for NotificationContext token
* make alias public readonly of UmbContextToken
* remove TODO
* use UmbContextToken::toString() for all stores
* use string alias for contexts
* move default data so we avoid importing a big lit library just to get default data interface
* add rollup to two extra libraries
* make sure we build uui and lit into our libraries for the few cases we import something
* add lockfile
* add separate options for .js files
* add function to install types of module
* add types output
* remove unused tsconfig-base file for now
* multiple selection in modalhandler is ok?
* installed view updates
* created view updates
* workspace for package builder
* package builder
* all pickers in workspace
* use input-picker rather than property editor ui
* installed package view
* ui updates
* packageview
* update handlers
* update package views with migrations
* update backend api
* endpoints
* migration & language picker
* small update
* seperate migrations that doesnt belong to a packag
* rename NotificationContext
* filter out packages that have no name before they go in to the store
---------
Co-authored-by: Jacob Overgaard <752371+iOvergaard@users.noreply.github.com>
