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.

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

Improve the import of other qface files #87

Open
Gagi2k opened this issue Sep 10, 2019 · 1 comment
Open

Improve the import of other qface files #87

Gagi2k opened this issue Sep 10, 2019 · 1 comment
Assignees
Milestone

Comments

@Gagi2k
Copy link
Collaborator

Gagi2k commented Sep 10, 2019

When importing another qface module, it is expected that this module is also parsed as part of FileSystem.parse(). If that's not the case, no error is reported, but instead the types can't be resolved in the templates.

If all the qface files are parsed, it would make sense to still be able to select which modules should be autogenerated and which modules are just needed to resolve the type simulation. This would make the system more flexible, as the user can define the structure of a big project and generate the modules one by one instead of doing it in one go.

@Gagi2k
Copy link
Collaborator Author

Gagi2k commented Oct 10, 2019

In addition it would be great if we could access the imported module directly from the domain model. Instead the the imports property just provides the import statement.

@jryannel jryannel added this to the Cleanup milestone Feb 12, 2020
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

No branches or pull requests

2 participants