meteor-feature-requests icon indicating copy to clipboard operation
meteor-feature-requests copied to clipboard

Proxies in Minimongo instead of automatic reactivity

Open janat08 opened this issue 7 years ago • 0 comments

Feature requests should include as much detail as possible:

  • [x] A description of the problem you're trying to solve, including why you think this is a problem Too much boilerplate, or you try and find reason for slow app performance on both client/server sides
  • [x] An overview of the suggested solution Use proxies to initiate reactive fields for publication. The economical solution being to simply insert projection for used fields by default, and I suppose for the edge cases where queries have been used to do simply recompute helper with nothing accessed publication could just emit recompute events, that is if no property was ever accessed.
  • [x] If the feature changes current behavior, reasons why your solution is better I hate this question.

See here for more detail on what is expected of a feature request.

janat08 avatar Jan 16 '18 07:01 janat08