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
{{ message }}
This repository has been archived by the owner on Sep 26, 2024. It is now read-only.
As a user of this awesome plugin,
I want to benefit from the hovering mechanism for external/imported needs,
So that I can more easily link external requirements.
Currently only possible to configure a single needs.json.
Would it perhaps make sense to be also able to configure further needs.json to that end?
The text was updated successfully, but these errors were encountered:
Yes, it totally makes sense.
Our use case is a little different, as we want to support multiple doc projects in one mono-repo.
So in the end we also need to register multiple needs.json files.
But getting a needs.json from external is also a great use case.
We are already starting to work on this, but as this feature needs a lot of architecture changes, it will take some time.
I know you are not necessarily working on that right now, but still one more thought:
It would make sense actually for external/imported needs just to pick up the json_path or json_url from needs_external_needs in the conf.py...
... from good to great ;-)
Thanks for the additional thoughts.
The multi-project support got already implemented, but it does not take external needs into account.
So this issue is still open.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As a user of this awesome plugin,
I want to benefit from the hovering mechanism for external/imported needs,
So that I can more easily link external requirements.
Currently only possible to configure a single
needs.json
.Would it perhaps make sense to be also able to configure further
needs.json
to that end?The text was updated successfully, but these errors were encountered: