Skip to content
This repository has been archived by the owner on Apr 22, 2024. It is now read-only.

Fix 338 - Warning message for no napps dir #343

Closed

Conversation

diraol
Copy link
Contributor

@diraol diraol commented Apr 11, 2017

No description provided.

@diraol diraol force-pushed the 338-warning-message-for-no-napp_dir branch 2 times, most recently from 763a5f3 to 7df4d17 Compare April 11, 2017 14:42
@diraol diraol force-pushed the 338-warning-message-for-no-napp_dir branch from 7df4d17 to 26d3716 Compare April 11, 2017 14:45
@diraol diraol requested a review from cemsbr April 11, 2017 19:37
@diraol
Copy link
Contributor Author

diraol commented Apr 11, 2017

@beraldoleal working now!

Copy link
Contributor

@cemsbr cemsbr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe a shorter log message would be better, but that's fine.

@beraldoleal
Copy link
Member

@diraol we are doing a huge refactoring on this. So I will hold this for a moment.

@beraldoleal
Copy link
Member

Thanks @diraol but since that we did a huge refactoring we already fixed this.

@diraol diraol deleted the 338-warning-message-for-no-napp_dir branch April 27, 2017 14:32
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants