Comments (5)
Hey, @camchenry. Thank you for yet another suggestion!
Would T | null
work for your use case? It'd be great to align the returned value, and we do use null
for update/delete operations already:
Lines 136 to 140 in f8da857
from data.
I have noticed this some day ago and put it in the pr #67. Today i'll rebase the branch
from data.
Yeah, T | null
would work for me, and I'd imagine others as well. For pretty much all intents and purposes, I'd treat null
and undefined
interchangeably. For me, the main thing is being able to use the ??
, and ?.
operators to handle nullish values seamlessly, as well as doing a check like:
const entity = db.entity.findFirst(...);
if (!entity) {
throw new Error(); // or return 404
}
// entity is now guaranteed to not be null/undefined
Thinking about it a little more though, this should probably only apply to the findFirst
function, because it returns the entity directly rather than an array of entities. Because findFirst
is analogous to Array.find
and findMany
is analogous to Array.filter
?
from data.
Agree on that: let's retain findMany
returning an empty array in the case when no entities matched the query. I find it a more pleasant data type to work with (both results.length
and results.map
are intuitive on empty results).
from data.
I believe with @67 merged findFirst
and findMany
now return the expected types:
Lines 129 to 141 in 5cc1d73
from data.
Related Issues (20)
- Can we store a literal object to an entity's field? HOT 8
- Using zod to generate table schema
- comparator missing for find by id
- Using wildcard/parameters in baseUrl in toHandlers method HOT 4
- Required oneOf relation HOT 6
- Poor performance when creating linked entities
- Database ID is not unique when extracted to a setup helper file (using Vitest) HOT 4
- Help Creating Type-Safe Models HOT 2
- Support transient attributes HOT 5
- Library's state and future HOT 13
- manyOf relationship in nullable objects HOT 1
- pnpm resolves msw optional dependency as v2 instead of v1 HOT 4
- Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'get') while generating handlers HOT 1
- Add toHandlers('json-api') support
- REST toHandlers() PUT and POST do not work with @mswjs/http-middleware due to req.body being a string
- Add the ability to set a foreign key on a model to create relationships HOT 1
- Make MSW/Data more type compatible with FakerJS functions HOT 1
- Typing issue when returning relation properties
- Faker definition for relationship properties
- Factory model for a Union Type model HOT 1
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 data.