-
Notifications
You must be signed in to change notification settings - Fork 7
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
Multiple context definition files #41
Comments
Contextive currently only supports a single definitions file - the file location is defined in the I'm open to adding support for multiple files (it would be relevant for #39 as well), but can you give a few more details on how you would like/expect it to work? A few questions to help hone in on the right solution:
Thanks! |
I imagined that it was unexpected behaviour, since the defintions.yml is indeed specified using that context.path. So, I was actually surprised that it kept working.
|
Hi @bluecitylights thanks for your thoughts on this. I agree that #37 is critical for when the context is distributed across multiple repos. I think there are three separate scenarios to consider:
Since we already have #39 and #37, I will create two new issues - one for scenario 2 and one for scenario 3 above, and close this issue, if that's ok with you? If there are other scenarios you think we should handle, please do let me know! Thanks :) |
This summary makes perfect sense to me. |
Great. Have itemised these matters into 4 separate issues, and marked them with the repo-layout label. From my interpretation of your situation above, item #37 is probably the highest priority for you - if you have further thoughts on how you'd like that to work, could you please add them there? Thanks! |
When I am in Vs code and split my big context file into multiple files, and delete default definition yml (one context each), everything keeps working. And the tool tips are based on the contents of all the definition files.
When you restart Vs code it complains that definitions file can not be found.
The text was updated successfully, but these errors were encountered: