Implements the necessary changes so json-based widgets/mashups can be loaded/created in wirecloud.
Creates mashups using a config.json properties file. Adds a jsonschema validator
Types of changes
What types of changes does your code introduce to the project: Put an x in the boxes that apply
[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules
Further comments
It would be interesting to change the config file to something unique instead of config.json so the JSON Schema can be sent to Schema Store to allow verifying the config file inside IDEs. Reopening this PR since the last one had some issues with files from another branch
coverage: 88.217% (+0.007%) from 88.21%
when pulling 9a404e80817c7735f7034d116ee5e89fbe774915 on dmunozv04:json-support
into 2a25766282456578de3663734a69b0281ed88bb8 on Wirecloud:develop.
Proposed changes
Implements the necessary changes so json-based widgets/mashups can be loaded/created in wirecloud. Creates mashups using a config.json properties file. Adds a jsonschema validator
Types of changes
What types of changes does your code introduce to the project: Put an
x
in the boxes that applyChecklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Further comments
It would be interesting to change the config file to something unique instead of config.json so the JSON Schema can be sent to Schema Store to allow verifying the config file inside IDEs. Reopening this PR since the last one had some issues with files from another branch