Issue with `observeAsync` in Meteor 3.0.4

[mcorbelli]

Title: Issue with observeAsync in Meteor 3.0.4 causing user object to revert to database state

Description:

There is a bug in Meteor 3.0.4 related to the publish of the currently logged-in user's information. I am using observeAsync to modify and add data to the user object before it is sent to the client. The issue arises when the modified user object, which prints correctly on the server before being sent, appears incorrect on the frontend.

Meteor Version:

Meteor 3.0.4

Last Working Version:

Not applicable (or specify if known)

Operating System:

MacOS 15.2

Expected Behavior:

The user object modified on the server using observeAsync should be sent to the client as-is, with no automatic overrides by the fields present in the database.

Actual Behavior:

The user object appears correct when printed on the server before being sent to the client. However, on the frontend, the modified fields (e.g., the profile field) are being overridden by the data from the database, which leads to discrepancies.

Steps to Reproduce:

1. Set up a publication with observeAsync to modify the user object.
2. Print the modified user object on the server before sending it to the client.
3. Check the client-side output of the user object.

Expected Result: The client receives the modified user object with the changes applied server-side. Actual Result: The client receives a user object where the modified fields are reverted to match the database state.

Reproduction:

A minimal reproduction can be provided if needed. Please let me know if it’s necessary.

[github-actions[bot]]

This issue has been automatically labeled as idle due to 90 days of inactivity. If this issue is still relevant, please comment to reactivate it.

[italojs]

is it still happen in > Meteor 3.3 ?