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 profile support #89

Open
Gagi2k opened this issue Oct 10, 2019 · 0 comments
Open

Improve profile support #89

Gagi2k opened this issue Oct 10, 2019 · 0 comments
Milestone

Comments

@Gagi2k
Copy link
Collaborator

Gagi2k commented Oct 10, 2019

Currently the profile support doesn't work as expected. I would expect to get errors if a qface file tries to import a module when using the micro profile, but at the moment only some additional warnings are provided (without context like file and line numbers), but the code is still generated as like the features were supported.

In addition the profiles don't work for all functions, e.g. the Generator.parse_document() function takes the filter and is also using it, while the Generator.parse() function takes the profile, but ignores it completely.

In addition to the predefined profiles, it would be great if the developer could define its own profile easily and just select the features he wants to support and maybe even a more advanced way to be able to hook into the listener and define own features (e.g. not support Interfaces as properties)

@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