Add some sort of service definition to validate and give intelligence to the provided services #5

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.

Sign up for GitHub

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

Jump to bottom

Open

bsears90 opened this issue Sep 13, 2017 · 0 comments

Labels

discussion required enhancement

Collaborator

bsears90 commented Sep 13, 2017 •

edited

Loading

A way of defining service schema's would be very useful especially for the more complex schemas that plugins will be providing.

Another thing to think about is versioning these service schemas so plugins can consume a specific version of a service.

some questions to answer if it is determined we need a service definition:

How to format a "service definition"
Should we be able to version and consume versions of service definition
How should service definitions be stored? As separate NPM modules? Embedded in plugins? Both?
do we want to handle redux actions that can be dispatched against services?

bsears90 added discussion required enhancement labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment