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

Handle different versions of TDs #14

Open
relu91 opened this issue Mar 14, 2022 · 1 comment
Open

Handle different versions of TDs #14

relu91 opened this issue Mar 14, 2022 · 1 comment

Comments

@relu91
Copy link
Member

relu91 commented Mar 14, 2022

optimally speaking we should find a way to handle both of the schemas... For example, use 1.1 if the @context has the right link to the new context. Anyhow, it is ok to be updated and use the latest version for now.

Originally posted by @relu91 in #13 (comment)

@egekorkan
Copy link
Member

Just for some information that might be useful here:

I have thought of finding a solution for this for Playground but I could not find a satisfying one. In the end, there will be a V1.0 playground hosted under another URL. That will not have any maintenance guarantees.

I think that in the case of this plugin, the user can specify it in the plugin settings. This would work if the user works mostly with one version of a TD.

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