[DOCS-14209] Realm Legacy sample code snippet doesn't match reference docs Created: 10/Feb/21 Updated: 30/Mar/21 Resolved: 30/Mar/21 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Realm |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Paolo Manna | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 2 years, 45 weeks, 1 day ago |
| Description |
DescriptionThe sample code snippet that illustrates event handling for Realm Legacy in Node.js uses indexes to cycle through all the modifications, and shows the requirement to fetch objects from the DB first. Since version 6 of the SDK, however, the ChangeEvent structure reports directly the modified objects instead of their indexes, avoiding the necessity of a fetch, so the handling is much easier. The sample code should be modified to reflect the change, as users are confused when they have code based on it. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Chris Bush [ 30/Mar/21 ] |
|
Thanks for raising. However, that documentation is no longer supported. |