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)
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)