-
Notifications
You must be signed in to change notification settings - Fork 603
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
[proposal] Internal mutateArgs
usage in core
#1529
base: master
Are you sure you want to change the base?
Conversation
…ing from .destroy(). (Still needs some love.)
…p the Archived model (which doesn't exist yet)
…me additional notes for future reference.
… the forging from the find query) so that the destroy() query works. Note: At this point, you can take this and use .archive() at the app-level in your own project, provided you hook up your own Archive model. But in subsequent commits, I'll write some code that injects this model automatically, unless configured otherwise.
… it's actually faster, otherwise no reason to include any of this extra complexity.
mutateArgs
could be used to hypothetically make queries faster by avoiding unnecessary object cloning internally. The next step is to benchmark this-- without benchmarks proving this is actually faster, it would be a mistake to merge this into core.mutateArgs
usage in core
This demonstrates how |
@sgress454 I reckon you're talking about .archive() right? (I think the PRs might have crossed streams) |
@mikermcneil I was commenting in the source, I guess the specific commit must be part of this PR... |
For more background, see https://trello.com/c/QapDT6XY/87-could-not-fetch-session-socket-has-no-cookie-in-its-handshake-edit-nevermind-see-updated-description