You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should be possible to 'split' a definitions file into multiple files even in a single repo (monorepo) configuration, so that teams that 'own' a context and also 'own' a folder structure within the monorepo can keep their definitions local to their context code and own the file containing their definitions.
Some initial ideas for how to implement this:
Add an 'import' mechanism to the central definitions file. Other files can be located wherever and can be 'imported' via a relative path into the overall definitions structure
Update the contextive.path setting to be a contextive.paths setting which lists a set of files to be loaded by contextive
A more convention oriented approach where the whole folder structure is scanned for a well defined filename (e.g. definitions.yml or contextive.yml so it would just be a matter of creating a file anywhere with the correct filename and it would get picked up
Related Tickets
This is related to #39, however that ticket is more focussed on supporting the multi-root workspace in VSCode, which carries with it extra considerations around handling scoped settings and resources. However, the facility to at least handle definitions coming from multiple files will likely support the implementation of #39.
The text was updated successfully, but these errors were encountered:
It should be possible to 'split' a definitions file into multiple files even in a single repo (monorepo) configuration, so that teams that 'own' a context and also 'own' a folder structure within the monorepo can keep their definitions local to their context code and own the file containing their definitions.
Some initial ideas for how to implement this:
contextive.path
setting to be acontextive.paths
setting which lists a set of files to be loaded by contextivedefinitions.yml
orcontextive.yml
so it would just be a matter of creating a file anywhere with the correct filename and it would get picked upRelated Tickets
This is related to #39, however that ticket is more focussed on supporting the multi-root workspace in VSCode, which carries with it extra considerations around handling scoped settings and resources. However, the facility to at least handle definitions coming from multiple files will likely support the implementation of #39.
The text was updated successfully, but these errors were encountered: