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
Right now we have two main ways that a set of field dependencies are usable:
Via the CLI via the plow protege command (downside: format specific to Protege)
Via the libraries (downside: not usable via the CLI)
To be better usable across a wide variety of tools it would be good to make the output of the dependency resolution and retrieval process accessible in an easy to digest way, which any other tools could integrate with.
E.g. we could have a plow install command, which places (or symlinks) the retrieved fields into a directory inside the workspace (e.g. plow_fields as an analogue to node_modules), together with metadata that would make it easy to load those fields.
The text was updated successfully, but these errors were encountered:
Right now we have two main ways that a set of field dependencies are usable:
plow protege
command (downside: format specific to Protege)To be better usable across a wide variety of tools it would be good to make the output of the dependency resolution and retrieval process accessible in an easy to digest way, which any other tools could integrate with.
E.g. we could have a
plow install
command, which places (or symlinks) the retrieved fields into a directory inside the workspace (e.g.plow_fields
as an analogue tonode_modules
), together with metadata that would make it easy to load those fields.The text was updated successfully, but these errors were encountered: