I think the reason was that I saw a lot of “junk” coming from these fields in my tests. As a way to support custom fields but also avoid them when not necessary I can propose two solutions:
Include in results custom fields that were explicitly specified in the query.
Have a flag in the query to control if custom fields should be included in results.
Thanks foor the reply! Both alternatives seem reasonable to me. The first one seems more efficient at runtime, the second one easier to implement. Both would definitely solve the issue.
Do you feel that one them could make it into the product in the forseeable future?