Open wreiske opened 1 month ago
Thank you for submitting this issue!
We, the Members of Meteor Community Packages take every issue seriously. Our goal is to provide long-term lifecycles for packages and keep up with the newest changes in Meteor and the overall NodeJs/JavaScript ecosystem.
However, we contribute to these packages mostly in our free time. Therefore, we can't guarantee your issues to be solved within certain time.
If you think this issue is trivial to solve, don't hesitate to submit a pull request, too! We will accompany you in the process with reviews and hints on how to get development set up.
Please also consider sponsoring the maintainers of the package. If you don't know who is currently maintaining this package, just leave a comment and we'll let you know
Describe the bug I'm running into an issue where this.userId is null when called from a Meteor.subscribe on the client, but is NOT null when using this.subscribe inside fast-render server side.
Expected behavior this.userId should always include the current logged in userId calling the subscription either called server side (like in fast-render) or client side (using Meteor.subscribe).
Example
Client Side
Fast Render
Using
communitypackages:fast-render@5.0.0-beta.0
Server Side Publication
Current Behavior https://github.com/Meteor-Community-Packages/meteor-publish-composite/commit/ec9f07755708166267b92772a8fd1838448b4208
With Meteor.bindEnvironment
Notice that the 'client' calls twice now. The second time it has the correct userId!!!!
IMO, Somewhere there is a bug that is causing this behavior... I am also running on about an hour of sleep so I may also be overlooking something simple.