Skip to content
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

Provide a specific name for Tech Extension model object json file #714

Closed
apupier opened this issue Dec 12, 2017 · 6 comments
Closed

Provide a specific name for Tech Extension model object json file #714

apupier opened this issue Dec 12, 2017 · 6 comments

Comments

@apupier
Copy link
Contributor

apupier commented Dec 12, 2017

it will allow to bind json schemas more easily.

@lburgazzoli
Copy link
Collaborator

@apupier can you give an example of what you'd expect ?

@apupier
Copy link
Contributor Author

apupier commented Dec 12, 2017

currently it is called extension-definition.json

I expect something very specific to Syndesis to avoid naming collisions as far as possible.
Two proposals:

  • syndesis-tech-extension-definition.json
  • syndesis-extension-definition.json

@lburgazzoli
Copy link
Collaborator

yeah but it is in a folder named syndesis

@apupier
Copy link
Contributor Author

apupier commented Dec 12, 2017

yeah but it is in a folder named syndesis

At least Eclipse JSON editor is based on the file name uniquely and I think that I see some Language Server Protocol for JSON doing the same (to check)

@lburgazzoli
Copy link
Collaborator

lburgazzoli commented Dec 12, 2017

ok, it is a little ugly but let's have the following naming:

  • syndesis/syndesis-extension-definition.json
  • syndesis/syndesis-extension-definition-schema.json

@apupier Is that ok ?

@apupier
Copy link
Contributor Author

apupier commented Dec 12, 2017

ok for me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants