-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not very helpful error on misconfiguration #42
Labels
Comments
This error occurs when there are cycling dependencies. I agree, we can display the path of the cycle instead of the cryptic message. |
buddhike
pushed a commit
to buddhike/mbt
that referenced
this issue
Mar 25, 2018
We display path of the cyclic reference in the error message. This should help the developers to find the misconfigured module easily and correct the problem. This change also includes the following changes. - Simplified the graph interface - Improved the source file organisation in graph module - Added tests for complex graphs Closes mbtproject#42
buddhike
pushed a commit
that referenced
this issue
Mar 25, 2018
We display path of the cyclic reference in the error message. This should help the developers to find the misconfigured module easily and correct the problem. This change also includes the following changes. - Simplified the graph interface - Improved the source file organisation in graph module - Added tests for complex graphs Closes #42
@dustyhorizon, Please checkout the build from dev channel and let me know if the new behaviour is satisfactory. |
Preview can be found here: https://media.giphy.com/media/2wYr5lhgZQKmKobv1Z/giphy.mp4 |
@BuddySpike looking good, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On misconfiguring
.mbt.yml
file by naming a module and referencing itself in dependencies in the same configuration, the following error is thrown:mbt should be able to identify which module is misconfigured and should throw an appropriate message with it.
The text was updated successfully, but these errors were encountered: