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 Mar 4, 2022. It is now read-only.
Hi,
One thing which can make prototool even better is custom config path.
In large projects there may be many configs for different tools and it would be extremely convenient to keep them all in a dedicated directory (e.g. configs) rather than cluttering repository's root.
Working directory is repo root.
The config path flag would be passed like: prototool generate --config configs/prototool.yaml
Prototool should work the same as if the config was in the working directory (i.e. repo root).
Please let me know what you think about this feature request.
P.S. There is a PR open already #519, but it seem to be left without attention.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
One thing which can make prototool even better is custom config path.
In large projects there may be many configs for different tools and it would be extremely convenient to keep them all in a dedicated directory (e.g.
configs
) rather than cluttering repository's root.Imagine the following project structure:
Working directory is repo root.
The config path flag would be passed like:
prototool generate --config configs/prototool.yaml
Prototool should work the same as if the config was in the working directory (i.e. repo root).
Please let me know what you think about this feature request.
P.S. There is a PR open already #519, but it seem to be left without attention.
The text was updated successfully, but these errors were encountered: