Replies: 3 comments
-
Thank you for the suggestion! Do you need aliases? I'm thinking that maybe there is a scenario that I have missed out on when analyzing the source code (using the data from lock files) and that should be fixed. Aliases should no longer be needed (that's my goal, at least 😄 ). |
Beta Was this translation helpful? Give feedback.
-
If you removed the need for aliases, that would be even better. Let me use the latest version, as I still use what is in the current documentation. I will come back to you. I have few libraries like that I know need aliases |
Beta Was this translation helpful? Give feedback.
-
(moving this to the Discussions and the Ideas section) |
Beta Was this translation helpful? Give feedback.
-
Is your feature request related to a problem? Please describe.
The current version of Polylith supports aliases to check dependencies. This is great, however it can start to be hard to keep track. It would be nice to have the ability to have all the aliases you need for your project under the configuration like
[tool.polylith.alias]
Describe the solution you'd like
Add a new configuration section in the
pyproject.toml
to manage aliasesAdditional context
We want to automate the check of the poly workspaces using pre-commit. however we don't want to have to maintain the list of aliases separately
PS: We will merge that back the pre-commit configuration after running it.
Beta Was this translation helpful? Give feedback.
All reactions