Closed noelmcloughlin closed 5 months ago
Hi @noelmcloughlin - I'm confused at the difference between this PR and this one: https://github.com/linkml/linkml-project-cookiecutter/blob/main/%7B%7Bcookiecutter.project_name%7D%7D/config.yaml :) can you help me figure out why we need both config.env and config.yaml? (maybe its just ease of use for folks more comfortable with env file vs. yaml?)
Ideally config.yaml
is enough and make setup
and make gendoc
are exhaustive.
However there are 3 issues where expected behavior does not match actual.
For long time I planned doing linkml demo to some colleagues, but working through few things first. So this project is good starting point - however, I would prefer not to maintain my own fork to address issues, so I proposed config.env
as short term workaround.
I'm also willing to raise issues for above and link to this PR
I corrupted my branch so closing - will have to redo
This PR allows user to trigger java and typescript generators via
config.env
andmake setup
because user might want them but gen-project excludes. Additional user can re-trigger owl generator if https://github.com/linkml/linkml/issues/1453 is an issue.Changes are transparent to existing users.
Once owl bug is fixed and gen-project includes java/ts then most of this PR could be reverted.