Skip to content

Conversation

Plamen5kov
Copy link
Contributor

@Plamen5kov Plamen5kov commented Sep 1, 2017

fix for #833

problem
When gradle can't find .js files to parse it doesn't show an ok Error, pointing out the problem

solution
Throw an error that describes the issue, in this case, to help the user figure out the problem.

@petekanev
Copy link
Contributor

@Plamen5kov Shouldn't we terminate the build with an exception? If no scripts have been parsed, then there likely won't be any scripts to run the application off of.

@ns-bot
Copy link

ns-bot commented Sep 1, 2017

💔

@Plamen5kov
Copy link
Contributor Author

I dont't know why I've put warning in the message .. we throw an error...

@Plamen5kov Plamen5kov force-pushed the plamen5kov/better-js-parsing-warnings branch from 4aa04a7 to 8833114 Compare September 1, 2017 13:45
@ns-bot
Copy link

ns-bot commented Sep 1, 2017

💚

@Plamen5kov Plamen5kov merged commit 8d849ea into master Sep 4, 2017
@Plamen5kov Plamen5kov deleted the plamen5kov/better-js-parsing-warnings branch September 4, 2017 05:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants