Skip to content
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.

Sign up for GitHub

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

Jump to bottom

At the end, check for other elm-package.json files in subdirectories and warn if they haven't been upgraded yet #7

Closed
avh4 opened this issue Nov 14, 2016 · 2 comments
Closed

At the end, check for other elm-package.json files in subdirectories and warn if they haven't been upgraded yet #7

avh4 opened this issue Nov 14, 2016 · 2 comments

Comments

@avh4
Copy link
Owner

avh4 commented Nov 14, 2016

(and recommend (cd that/folder; elm-upgrade)
@avh4 avh4 mentioned this issue Nov 16, 2016
Closed
@HappMacDonald
Copy link

How about the elm-package.json in a testing folder? Should that get slurped into the top level elm.json instead of a warning? :)

@avh4
Copy link
Owner Author

avh4 commented Sep 3, 2018

In Elm 0.19, tests/elm-package.json will get merged into elm.json (see #47). With that change, this issue doesn't really make much sense any more, and also no one has ever really asked for this feature.

@avh4 avh4 closed this as completed Sep 3, 2018
avh4 added a commit that referenced this issue Sep 3, 2018
@avh4
Configure Appveyor CI (attempt #7)
7571f75
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@avh4 @HappMacDonald