Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / Papooch/nestjs-cls issues and pull requests
#188 - Issue to configure knexInstanceToken in NestJS
Issue -
State: open - Opened by ClaraGr 4 days ago
#187 - CLS not active in a NestJS Hybrid RPC interceptor test
Issue -
State: closed - Opened by keymatch-clovis 10 days ago
- 2 comments
Labels: question, solved
#186 - Feature Request: Transactional: Support Promises in `withTransaction` for Batch Query
Issue -
State: closed - Opened by pknameer 17 days ago
- 3 comments
Labels: enhancement, question, wontfix
#185 - feat(transactional-adapter-mikro-orm): add mikro orm adapter
Pull Request -
State: open - Opened by whileloop99 17 days ago
#184 - In prisma's $on event, nest-cls did not get normal context data
Issue -
State: closed - Opened by ahuijiLearning 25 days ago
- 1 comment
Labels: external bug
#183 - Is there a way to manually eject out of a transaction without raising an error?
Issue -
State: closed - Opened by ThomasShih about 1 month ago
- 5 comments
Labels: question
#182 - build: update ts settings
Pull Request -
State: closed - Opened by Papooch about 1 month ago
#181 - Prisma transactional plugin connection usage
Issue -
State: closed - Opened by xtrinch about 2 months ago
- 3 comments
Labels: not a bug
#180 - feat(transactional-adapter-drizzle-orm): add drizzle orm adapter
Pull Request -
State: closed - Opened by Papooch about 2 months ago
#179 - feat(drizzle): add basic support for drizzle-orm postgres
Pull Request -
State: closed - Opened by fjanicki about 2 months ago
- 5 comments
#176 - Potential nest-js cls plugin: `@Rollbackable()`
Issue -
State: closed - Opened by drakedeatonuk 2 months ago
- 5 comments
Labels: enhancement, wontfix
#173 - docs: fix guard to interceptor
Pull Request -
State: closed - Opened by JangDaljin 4 months ago
- 1 comment
#172 - fix(core): support primitive values in websocket payload
Pull Request -
State: closed - Opened by Papooch 4 months ago
#171 - feat: enable `strict` mode for Proxy Providers
Pull Request -
State: closed - Opened by Papooch 4 months ago
#171 - feat: enable `strict` mode for Proxy Providers
Pull Request -
State: closed - Opened by Papooch 4 months ago
#170 - WebSocket data can be a primitive, causing exception
Issue -
State: open - Opened by alberto-i 4 months ago
- 1 comment
Labels: bug
#170 - WebSocket data can be a primitive, causing exception
Issue -
State: open - Opened by alberto-i 4 months ago
- 1 comment
Labels: bug
#170 - WebSocket data can be a primitive, causing exception
Issue -
State: open - Opened by alberto-i 4 months ago
- 1 comment
Labels: bug
#170 - WebSocket data can be a primitive, causing exception
Issue -
State: closed - Opened by alberto-i 4 months ago
- 2 comments
Labels: bug, solved
#169 - Add proper support for injecting proxy providers into other proxy providers
Issue -
State: open - Opened by Papooch 4 months ago
Labels: enhancement
#169 - Add proper support for injecting proxy providers into other proxy providers
Issue -
State: open - Opened by Papooch 4 months ago
Labels: enhancement
#168 - When generating id for RPC using interceptor I get the whole context instead of "request data"
Issue -
State: closed - Opened by micgre0 4 months ago
- 1 comment
Labels: question, solved
#168 - When generating id for RPC using interceptor I get the whole context instead of "request data"
Issue -
State: closed - Opened by micgre0 4 months ago
- 1 comment
Labels: question, solved
#168 - When generating id for RPC using interceptor I get the whole context instead of "request data"
Issue -
State: closed - Opened by micgre0 4 months ago
- 1 comment
Labels: question, solved
#168 - When generating id for RPC using interceptor I get the whole context instead of "request data"
Issue -
State: closed - Opened by micgre0 4 months ago
- 1 comment
Labels: question, solved
#168 - When generating id for RPC using interceptor I get the whole context instead of "request data"
Issue -
State: closed - Opened by micgre0 4 months ago
- 1 comment
Labels: question, solved
#167 - fix(transactional)!: correct behavior of `Propagation.Never`
Pull Request -
State: open - Opened by Papooch 4 months ago
#167 - fix(transactional): correct behavior of `Propagation.Never`
Pull Request -
State: closed - Opened by Papooch 4 months ago
#167 - fix(transactional)!: correct behavior of `Propagation.Never`
Pull Request -
State: open - Opened by Papooch 4 months ago
#167 - fix(transactional)!: correct behavior of `Propagation.Never`
Pull Request -
State: open - Opened by Papooch 4 months ago
#167 - fix(transactional)!: correct behavior of `Propagation.Never`
Pull Request -
State: open - Opened by Papooch 4 months ago
#166 - Add an option to forbid active transactions in specific methods (@nestjs-cls/transactional)
Issue -
State: open - Opened by fredsensibill 4 months ago
- 7 comments
Labels: enhancement
#166 - Add an option to forbid active transactions in specific methods (@nestjs-cls/transactional)
Issue -
State: open - Opened by fredsensibill 4 months ago
- 7 comments
Labels: enhancement
#166 - Add an option to forbid active transactions in specific methods (@nestjs-cls/transactional)
Issue -
State: open - Opened by fredsensibill 4 months ago
- 7 comments
Labels: enhancement
#166 - Add an option to forbid active transactions in specific methods (@nestjs-cls/transactional)
Issue -
State: open - Opened by fredsensibill 4 months ago
- 7 comments
Labels: enhancement
#166 - Add an option to forbid active transactions in specific methods (@nestjs-cls/transactional)
Issue -
State: closed - Opened by fredsensibill 4 months ago
- 8 comments
Labels: enhancement, solved
#166 - Add an option to forbid active transactions in specific methods (@nestjs-cls/transactional)
Issue -
State: open - Opened by fredsensibill 4 months ago
- 7 comments
Labels: enhancement
#166 - Add an option to forbid active transactions in specific methods (@nestjs-cls/transactional)
Issue -
State: open - Opened by fredsensibill 4 months ago
- 7 comments
Labels: enhancement
#166 - Add an option to forbid active transactions in specific methods (@nestjs-cls/transactional)
Issue -
State: open - Opened by fredsensibill 4 months ago
- 7 comments
Labels: enhancement
#165 - mongoose adapter support Propagation.NotSupported mode
Issue -
State: closed - Opened by GO-DIE 5 months ago
- 3 comments
Labels: needs info, stale
#164 - Support for Mikro-ORM
Issue -
State: open - Opened by vroudge 5 months ago
- 1 comment
Labels: enhancement
#164 - Support for Mikro-ORM
Issue -
State: open - Opened by vroudge 5 months ago
- 2 comments
Labels: enhancement, contribution welcome
#164 - Support for Mikro-ORM
Issue -
State: open - Opened by vroudge 5 months ago
- 1 comment
Labels: enhancement
#164 - Support for Mikro-ORM
Issue -
State: open - Opened by vroudge 5 months ago
- 1 comment
Labels: enhancement
#164 - Support for Mikro-ORM
Issue -
State: open - Opened by vroudge 5 months ago
- 1 comment
Labels: enhancement
#164 - Support for Mikro-ORM
Issue -
State: open - Opened by vroudge 5 months ago
- 1 comment
Labels: enhancement, contribution welcome
#164 - Support for Mikro-ORM
Issue -
State: open - Opened by vroudge 5 months ago
- 1 comment
Labels: enhancement
#164 - Support for Mikro-ORM
Issue -
State: open - Opened by vroudge 5 months ago
- 1 comment
Labels: enhancement
#164 - Support for Mikro-ORM
Issue -
State: open - Opened by vroudge 5 months ago
- 1 comment
Labels: enhancement
#163 - Nest can't resolve dependencies of the ClsModule (?, ModuleRef). Please make sure that the argument HttpAdapterHost at index [0] is available in the ClsModule context. (Using PNPM)
Issue -
State: closed - Opened by RabahZeineddine 5 months ago
- 10 comments
Labels: not a bug, solved
#163 - Nest can't resolve dependencies of the ClsModule (?, ModuleRef). Please make sure that the argument HttpAdapterHost at index [0] is available in the ClsModule context. (Using PNPM)
Issue -
State: closed - Opened by RabahZeineddine 5 months ago
- 10 comments
Labels: not a bug, solved
#163 - Nest can't resolve dependencies of the ClsModule (?, ModuleRef). Please make sure that the argument HttpAdapterHost at index [0] is available in the ClsModule context. (Using PNPM)
Issue -
State: closed - Opened by RabahZeineddine 5 months ago
- 10 comments
Labels: not a bug, solved
#163 - Nest can't resolve dependencies of the ClsModule (?, ModuleRef). Please make sure that the argument HttpAdapterHost at index [0] is available in the ClsModule context. (Using PNPM)
Issue -
State: closed - Opened by RabahZeineddine 5 months ago
- 10 comments
Labels: not a bug, solved
#163 - Nest can't resolve dependencies of the ClsModule (?, ModuleRef). Please make sure that the argument HttpAdapterHost at index [0] is available in the ClsModule context. (Using PNPM)
Issue -
State: closed - Opened by RabahZeineddine 5 months ago
- 10 comments
Labels: not a bug, solved
#163 - Nest can't resolve dependencies of the ClsModule (?, ModuleRef). Please make sure that the argument HttpAdapterHost at index [0] is available in the ClsModule context. (Using PNPM)
Issue -
State: closed - Opened by RabahZeineddine 5 months ago
- 10 comments
Labels: not a bug, solved
#163 - Nest can't resolve dependencies of the ClsModule (?, ModuleRef). Please make sure that the argument HttpAdapterHost at index [0] is available in the ClsModule context. (Using PNPM)
Issue -
State: closed - Opened by RabahZeineddine 5 months ago
- 10 comments
Labels: not a bug, solved
#163 - Nest can't resolve dependencies of the ClsModule (?, ModuleRef). Please make sure that the argument HttpAdapterHost at index [0] is available in the ClsModule context. (Using PNPM)
Issue -
State: closed - Opened by RabahZeineddine 5 months ago
- 10 comments
Labels: not a bug, solved
#163 - Nest can't resolve dependencies of the ClsModule (?, ModuleRef). Please make sure that the argument HttpAdapterHost at index [0] is available in the ClsModule context. (Using PNPM)
Issue -
State: closed - Opened by RabahZeineddine 5 months ago
- 10 comments
Labels: not a bug, solved
#162 - docs: fix title in readme
Pull Request -
State: closed - Opened by Papooch 5 months ago
#161 - feat(transactional-adapter-mongodb): add `mongodb` adapter
Pull Request -
State: closed - Opened by Papooch 5 months ago
#160 - feat(transactional): enable adapters to opt out of transactional proxy support
Pull Request -
State: closed - Opened by Papooch 5 months ago
#159 - feat(transactional-adapter-mongoose): add `mongoose` adapter
Pull Request -
State: closed - Opened by Papooch 5 months ago
#158 - feat(transactional-adapter-mongodb): add `mongodb` adapter
Pull Request -
State: closed - Opened by Papooch 5 months ago
#157 - chore(transactional): add more tests for transactional adapters
Pull Request -
State: closed - Opened by Papooch 5 months ago
#156 - feat(transactional): enable lifecycle hooks in TransactionalAdapter
Pull Request -
State: closed - Opened by Papooch 5 months ago
#155 - Support for Drizzle ORM
Issue -
State: closed - Opened by herenickname 5 months ago
- 6 comments
Labels: enhancement, contribution welcome
#154 - Add transactional adapter support for mongoose
Issue -
State: closed - Opened by GO-DIE 5 months ago
- 4 comments
Labels: enhancement
#153 - chore: add link to discord server on issue template
Pull Request -
State: closed - Opened by micalevisk 6 months ago
#152 - Can't disconnect from DB while testing and using transactional plugin
Issue -
State: closed - Opened by Peterculazh 7 months ago
- 4 comments
Labels: not a bug, solved
#151 - Nest can't resolve dependencies of the ClsModule (?, ModuleRef). Please make sure that the argument HttpAdapterHost at index [0] is available in the ClsModule context.
Issue -
State: closed - Opened by Nijinsha 7 months ago
- 1 comment
#150 - fix(transactional): use proxy on descriptor.value
Pull Request -
State: closed - Opened by nicobuzeta 7 months ago
- 3 comments
#149 - @Transactional decorator breaking swagger documentation
Issue -
State: closed - Opened by nicobuzeta 7 months ago
- 2 comments
Labels: bug
#148 - setup / generateId functions not called in WebSocket Gateway
Issue -
State: closed - Opened by sagi-orchid 7 months ago
- 4 comments
Labels: investigation, not a bug, solved
#147 - transactional-adapter-pg-promise: where are the default tx options merged with tx-specific options?
Issue -
State: closed - Opened by sam-artuso 7 months ago
- 4 comments
Labels: investigation, not a bug, solved
#146 - CLS appears not running inside jest integration tests
Issue -
State: closed - Opened by gregoryorton-ws 7 months ago
- 2 comments
Labels: external bug
#145 - feat(transactional): add default options parameter to transactional adapter
Pull Request -
State: closed - Opened by Papooch 7 months ago
#144 - docs: update docs on transactional plugin
Pull Request -
State: closed - Opened by Papooch 7 months ago
#143 - chore: update typeorm adapter, add docs
Pull Request -
State: closed - Opened by Papooch 7 months ago
#142 - Use custom prisma client with prisma provider that is using `useFactory` method.
Issue -
State: closed - Opened by adrianlocurciohotovo 8 months ago
- 2 comments
Labels: not a bug, solved
#141 - Add typeorm Adapter for @nestjs-cls/transactional #140
Pull Request -
State: closed - Opened by giosueDelgado 8 months ago
- 4 comments
#140 - Add typeorm Adapter for @nestjs-cls/transactional
Issue -
State: closed - Opened by giosueDelgado 8 months ago
- 8 comments
Labels: enhancement
#139 - How to get a real database transaction in a test environment?
Issue -
State: closed - Opened by sam-artuso 8 months ago
- 2 comments
Labels: invalid
#138 - Update index.md
Pull Request -
State: closed - Opened by sam-artuso 8 months ago
#137 - Docker Error
Issue -
State: closed - Opened by shauntrennery 8 months ago
- 5 comments
Labels: investigation, needs info, stale
#136 - PgPromise adapter: add default tx options
Pull Request -
State: closed - Opened by sam-artuso 8 months ago
- 5 comments
#135 - chore: update deps + add test cases
Pull Request -
State: closed - Opened by Papooch 8 months ago
#134 - Global middleware not running on Nest > 10.3.2 (fastify, global prefix)
Issue -
State: closed - Opened by xtrinch 8 months ago
- 8 comments
Labels: external bug
#131 - feat: selectively resolve proxy providers
Pull Request -
State: closed - Opened by Papooch 8 months ago
Labels: enhancement
#131 - feat: selectively resolve proxy providers
Pull Request -
State: closed - Opened by Papooch 8 months ago
Labels: enhancement
#130 - Expose resolveProxyProvider function as we expose resolveProxyProviders
Issue -
State: closed - Opened by jpamorimdev 9 months ago
- 5 comments
Labels: enhancement
#130 - Expose resolveProxyProvider function as we expose resolveProxyProviders
Issue -
State: closed - Opened by jpamorimdev 9 months ago
- 7 comments
Labels: enhancement
#129 - fix: prevent context from leaking with ClsGuard
Pull Request -
State: closed - Opened by Papooch 9 months ago
#128 - chore: enable typescript strict mode
Pull Request -
State: closed - Opened by Papooch 9 months ago
#127 - Duplicate IDs when using Microservices (Kafka)
Issue -
State: closed - Opened by hjf 9 months ago
- 2 comments
Labels: bug
#127 - Duplicate IDs when using Microservices (Kafka)
Issue -
State: closed - Opened by hjf 9 months ago
- 2 comments
Labels: bug
#126 - feat: enable setting custom prisma client type for adapter
Pull Request -
State: closed - Opened by Papooch 9 months ago
#126 - feat: enable setting custom prisma client type for adapter
Pull Request -
State: open - Opened by Papooch 9 months ago
#126 - feat: enable setting custom prisma client type for adapter
Pull Request -
State: open - Opened by Papooch 9 months ago
#125 - How to use with extended client?
Issue -
State: closed - Opened by darr1s 10 months ago
- 2 comments
Labels: question, solved
#124 - feat: add option to inject tx directly as Proxy
Pull Request -
State: closed - Opened by Papooch 10 months ago