-
-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
added enhanced adapter license info to schema and types #2591
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we really reuse the license field? I think we show the license in admin already ... how old admin versions will react ifd the content is an object rather then a string?
Please sync with @bluefox and @UncleSamSwiss (?) too if current license field gets cahnged as adapter checker and dev portal need to be adapted ruther fast to avoid possible false positives. |
@mcm1957 as it will break admin, we will go with a new flag and deprecate the "old one", which is duplicated to the pack.json attribute anyway. We also made the new field "mandatory" in the schema. We will likely need adapter checker update (?) and update of adapter creator. Creator should simply default to type |
* added license info * fix update license script * format * deprecate common.license and introduce common.licenseInformation * rm local schema from controller iopack * bring back license for adapter tests
* optimize the upload procedure (#2589) - closes #2538 * fixed problem that cb is never called on mh enable/disable (#2557) * fixed problem that cb is never called on mh enable/disable * fix type * added enhanced adapter license info to schema and types (#2591) * added license info * fix update license script * format * deprecate common.license and introduce common.licenseInformation * rm local schema from controller iopack * bring back license for adapter tests * WIP placeholder added * prevent issue when values with stateNs.null exist in the database (#2580) * prevent issue when values with stateNs.null exist in the database - closes #2579 * rm log * rm anoither log * allow path aliases in adapter package * rm types from validator again * move tsc-alias to postbuild * use lerna to build project again as npm workspaces does not use the correct build script when building dependency packages - and using normal workspace flag works but is ineffective and can lead to errors due to still open npm/rfcs#548 * update jsonl * ts back to v4, accidentaly chosen by resolving merge conflict * build local * clean install to try to solve install module not found * another pack-lock update * fix linter
No description provided.