-
Notifications
You must be signed in to change notification settings - Fork 65
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
morphir-elm should fail if an exposed module does not exist #1172
Comments
duane
changed the title
morphir-elm should fail if an exposed path does not exist
morphir-elm should fail if an exposed module does not exist
Aug 8, 2024
AttilaMihaly
added a commit
to AttilaMihaly/morphir-elm
that referenced
this issue
Nov 13, 2024
AttilaMihaly
added a commit
to AttilaMihaly/morphir-elm
that referenced
this issue
Nov 13, 2024
AttilaMihaly
added a commit
to AttilaMihaly/morphir-elm
that referenced
this issue
Nov 13, 2024
AttilaMihaly
added a commit
to AttilaMihaly/morphir-elm
that referenced
this issue
Nov 26, 2024
AttilaMihaly
added a commit
to AttilaMihaly/morphir-elm
that referenced
this issue
Dec 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
I spent a good deal of time trying to debug why my type wasn't showing up in a generated IR file only to find I had exposed the wrong path to the module.
Describe the solution you'd like
Ideally, morphir-elm would verify that all exposed modules actually exist, and fail if they do not.
Describe alternatives you've considered
A warning would be fine, too.
🥂
The text was updated successfully, but these errors were encountered: