Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User#callFunction signature is different between Realm JS & Realm Web #3829

Closed
kraenhansen opened this issue Jul 6, 2021 · 1 comment
Closed
Labels

Comments

@kraenhansen
Copy link
Member

kraenhansen commented Jul 6, 2021

Goals

A unified API across Realm JS and Realm Web.

Expected Results

A user would expect to be able to call a remote function using the callFunction method on a User in the same way, regardless of them using Realm JS or Realm Web.

Actual Results

Where Realm JS takes two parameters (the name of the function and an array of arguments), Realm Web takes a name and an unbound number of arguments. This should be aligned - I suggest updating Realm Web to match the Realm JS implementation.

Version of Realm and Tooling

  • Realm JS SDK Version: Realm JS v10.5.0 & Realm Web v1.3.0.
  • Node or React Native: N/A
  • Client OS & Version: N/A
  • Which debugger for React Native: N/A
@kraenhansen
Copy link
Member Author

I consider this a duplicate of #3733

@sync-by-unito sync-by-unito bot closed this as completed Aug 16, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 16, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant