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

Orphan Juvix files can have any module name #2510

Closed
jonaprieto opened this issue Nov 10, 2023 · 0 comments · Fixed by #2512
Closed

Orphan Juvix files can have any module name #2510

jonaprieto opened this issue Nov 10, 2023 · 0 comments · Fixed by #2512
Assignees
@jonaprieto
Labels
bug modules
Milestone
0.5.4

Comments

@jonaprieto
Copy link
Collaborator

As the title says. How to reproduce this bug:

  • Create a file named A.juvix in a directory without juvix.yaml or Package.juvix. Declare a module named B in A.juvix.

This file type checks when it shouldn't.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jonaprieto jonaprieto

Labels
bug modules
Projects
None yet
Milestone
0.5.4
Development

Successfully merging a pull request may close this issue.

Fix check for module name for Orphan Juvix files and imports of Juvix Markdown files anoma/juvix
1 participant
@jonaprieto