nestjs-query icon indicating copy to clipboard operation
nestjs-query copied to clipboard

Easy CRUD for GraphQL.

Results 60 nestjs-query issues
Sort by recently updated
recently updated
newest added

**Describe the bug** I have an issue where I have two relationships with an `action` where calling setRelations passing in `[]` when the entity is company results in ALL companies...

bug

See https://github.com/TriPSs/nestjs-query/issues/270

**Describe the bug** We discovered an issue when sorting by a field with `null` values while using the `PagingStrategies.CURSOR` strategy. The issue manifests itself as no additional items loading beyond...

bug

**Describe the bug** I'm using an entity with composite primary keys. Those primary keys are not used in the generated schema for the read-one, update-one, and delete-one queries/mutations. ### Have...

bug

**Is your feature request related to a problem? Please describe.** Hey 👋 @TriPSs I saw your [feature request](https://github.com/doug-martin/nestjs-query/issues/1434) in the original project by Doug Martin. This is a similar situation...

enhancement

## 📚 Documentation We need an example in the documentation of how to work with inherited entities. There are two Entities in the same table. How do I make `FilterableUnpagedRelation`...

documentation

Bumps [dset](https://github.com/lukeed/dset) from 3.1.2 to 3.1.4. Release notes Sourced from dset's releases. v3.1.3 Patches Add "types" export conditions for TypeScript "nodenext"/"node16" resolution: #40 Thank you @​Akkuma Full Changelog: https://github.com/lukeed/dset/compare/v3.1.2...v3.1.3 Commits...

dependencies

more of a question... in the implementation of subscriptions, is there a mechanism for pruning old subscriptions? While front ends SHOULD unsubscribe, often they do not. Here is some rough...

documentation

**Is your feature request related to a problem? Please describe.** I have a column defined as ``` @Column({ type: 'text', array: true, default: [] }) userIDs: string[] ``` I would...

enhancement

by now querying entities with LIKE or iLIKE operator will always get the same results no matter if wildcards are set at the beginning or end. (e.g. `{like: 'test'}` and...