Comments (2)
@opsb Very cool to hear about your Firebase source!
As long as retrieve
works synchronously on a source, it should not need a cache. I plan to make the cache completely optional on the base Source
class.
However, I would not recommend placing a cache at the ember-orbit Store
level, which would require that your orbit source only work with ember-orbit and somehow be aware of the associated Store. Its important that retrieve
work on the Source level inside Orbit, so that transform connectors can inspect sources to compare their contents and determine which changes are needed. This doesn't mean that each source have a cache - just that retrieve
work synchronously (and the easiest way to achieve this initially was to put a cache on each source).
from orbit.
"so that transform connectors can inspect sources to compare their contents and determine which changes are needed. " aha, I did wonder about this, I hadn't figured out how Orbit stopped operations from bouncing backwards and forwards, makes a lot of sense now.
from orbit.
Related Issues (20)
- [Docs] Add search to docs site
- Memory Cache won't update relationships' meta if identities match existing record HOT 6
- Enable GitHub discussions to move support requests/general questions out of issue queue HOT 2
- [Docs] Add technical description of key request-processing, sync components
- `JSONAPIURLBuilder::buildPageParam()` (and likely others) have undefined properties serialized as `undefined` in query param
- Improve Validation Errors
- Integration with AbortSignal HOT 1
- serializers customization HOT 1
- custom filter operations
- [Feature] AsyncStorage data source
- Allow filtering for attribute/relationship not `null` (negated condition)
- Add "sideEffects": false to Orbit packages HOT 3
- Need optional chaining in `MemoryCache::removeInverseRelationshipsSync()` HOT 4
- jsonapi parallel request HOT 1
- parallel data querying principes HOT 3
- There is no upgrading steps in documentation HOT 2
- JSONAPISource Serialization Problem
- Store `__inverseRels__` not cleaned up with transform option `{ useBuffer: true }` HOT 1
- Optimistic Error Handling Got TypeError Not NetworkError HOT 4
- "supportsIndexedDB" is malfunctioning in some cases
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from orbit.