Michał Zendran
Michał Zendran
@filipenevola @radekmie As for my investigation I can confirm - it looks like meteor specific. It starts to occur in Meteor 2.2.3.
Problem still present in meteor v2.6.1
@renanccastro @filipenevola Since the problem wasn't solved by the new release, are there any other suggestions?
@fredmaiaarantes @zodern Since the problem is still present, can we have some eyes on it?
@afrokick Thank you for the workaround and the explanation - it works just fine.
Hi @soolidtech, thanks for your suggestion and for providing reproduction. For now ,our priority is to finalize release of version `2.0.0` so we will take care of it within the...
Solved in #1206. As no requirements for the template were added in this issue description, I've added 2 templates: 1. One for the feature request 2. One for the type...
@Panquesito7 @appgurueu Since there is not much time until the end of the Hactoberfest, would you mind adding the `hacktoberfest-accepted` label to this PR? I will add any required code-review...
For anyone looking for a workaround, restricting the npm version in the project helped: ``` "engines": { "npm": ">=8
No solution yet but, it seems the problem is the recursive nature of the `resolveRefIfNeeded` function used in the `getField` method. In the initial iteration, in the `resolveRef` function, the...