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.

Sign up for GitHub

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

Jump to bottom

feat: NotificationManager should accept a flag for whether a change to local vs remote state results in the notification #9688

Open
runspired opened this issue Feb 22, 2025 · 0 comments
Open

feat: NotificationManager should accept a flag for whether a change to local vs remote state results in the notification #9688

runspired opened this issue Feb 22, 2025 · 0 comments
Labels
🏷️ bug This PR primarily fixes a reported issue 🏷️ feat This PR introduces a new feature

Comments

@runspired
Copy link
Contributor

runspired commented Feb 22, 2025 •
edited
Loading

now that SchemaRecord only shows remote state by-default, updates generated by changes to local-state are unnecessary.

additionally: updates resulting from application of local state become necessary where before they were unnecessary (this is essentially a bug in the SchemaRecord world).

having separate channels will enable better performance tuning
@github-project-automation github-project-automation bot moved this to needs triage in EmberData Feb 22, 2025
@runspired runspired added 🏷️ feat This PR introduces a new feature 🏷️ bug This PR primarily fixes a reported issue labels Feb 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🏷️ bug This PR primarily fixes a reported issue 🏷️ feat This PR introduces a new feature
Projects
EmberData
Status: needs triage
Milestone
No milestone
Development

No branches or pull requests
1 participant
@runspired