Repository: nestjs/mongoose Branch: master Commit: 14b4e19837f2 Files: 81 Total size: 85.9 KB Directory structure: gitextract_f_tnf46s/ ├── .circleci/ │ └── config.yml ├── .commitlintrc.json ├── .github/ │ ├── ISSUE_TEMPLATE/ │ │ ├── Bug_report.yml │ │ ├── Feature_request.yml │ │ ├── Regression.yml │ │ └── config.yml │ └── PULL_REQUEST_TEMPLATE.md ├── .gitignore ├── .husky/ │ ├── .gitignore │ ├── commit-msg │ └── pre-commit ├── .npmignore ├── .prettierrc ├── .release-it.json ├── CONTRIBUTING.md ├── LICENSE ├── README.md ├── docker-compose.yml ├── eslint.config.mjs ├── lib/ │ ├── common/ │ │ ├── index.ts │ │ ├── mongoose.decorators.ts │ │ └── mongoose.utils.ts │ ├── decorators/ │ │ ├── index.ts │ │ ├── prop.decorator.ts │ │ ├── schema.decorator.ts │ │ └── virtual.decorator.ts │ ├── errors/ │ │ ├── cannot-determine-type.error.ts │ │ └── index.ts │ ├── factories/ │ │ ├── definitions.factory.ts │ │ ├── index.ts │ │ ├── schema.factory.ts │ │ └── virtuals.factory.ts │ ├── index.ts │ ├── interfaces/ │ │ ├── async-model-factory.interface.ts │ │ ├── index.ts │ │ ├── model-definition.interface.ts │ │ └── mongoose-options.interface.ts │ ├── metadata/ │ │ ├── property-metadata.interface.ts │ │ ├── schema-metadata.interface.ts │ │ └── virtual-metadata.interface.ts │ ├── mongoose-core.module.ts │ ├── mongoose.constants.ts │ ├── mongoose.module.ts │ ├── mongoose.providers.ts │ ├── pipes/ │ │ ├── index.ts │ │ ├── is-object-id.pipe.ts │ │ └── parse-object-id.pipe.ts │ ├── storages/ │ │ └── type-metadata.storage.ts │ └── utils/ │ ├── index.ts │ ├── is-target-equal-util.ts │ └── raw.util.ts ├── package.json ├── renovate.json ├── tests/ │ ├── e2e/ │ │ ├── discriminator.spec.ts │ │ ├── mongoose-lazy-connection.spec.ts │ │ ├── mongoose.spec.ts │ │ ├── schema-definitions.factory.spec.ts │ │ ├── schema.factory.spec.ts │ │ └── virtual.factory.spec.ts │ ├── jest-e2e.json │ └── src/ │ ├── app.module.ts │ ├── cats/ │ │ ├── cat.controller.ts │ │ ├── cat.module.ts │ │ ├── cat.service.ts │ │ ├── cats.controller.ts │ │ ├── cats.module.ts │ │ ├── cats.service.ts │ │ ├── dto/ │ │ │ └── create-cat.dto.ts │ │ └── schemas/ │ │ └── cat.schema.ts │ ├── event/ │ │ ├── dto/ │ │ │ ├── create-click-link-event.dto.ts │ │ │ └── create-sign-up-event.dto.ts │ │ ├── event.controller.ts │ │ ├── event.module.ts │ │ ├── event.service.ts │ │ └── schemas/ │ │ ├── click-link-event.schema.ts │ │ ├── event.schema.ts │ │ └── sign-up-event.schema.ts │ ├── lazy-app.module.ts │ └── main.ts ├── tsconfig.build.json └── tsconfig.json ================================================ FILE CONTENTS ================================================ ================================================ FILE: .circleci/config.yml ================================================ version: 2 aliases: - &restore-cache restore_cache: key: dependency-cache-{{ checksum "package.json" }} - &install-deps run: name: Install dependencies command: npm install --ignore-scripts - &build-packages run: name: Build command: npm run build jobs: build: working_directory: ~/nest docker: - image: cimg/node:24.13.0 steps: - checkout - restore_cache: key: dependency-cache-{{ checksum "package.json" }} - run: name: Install dependencies command: npm install --ignore-scripts - save_cache: key: dependency-cache-{{ checksum "package.json" }} paths: - ./node_modules - run: name: Build command: npm run build integration_tests: working_directory: ~/nest machine: true steps: - checkout - run: name: Prepare nvm command: | echo 'export NVM_DIR="/opt/circleci/.nvm"' >> $BASH_ENV echo ' [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"' >> $BASH_ENV - run: name: Upgrade Node.js command: | nvm install v20 node -v nvm alias default v20 - run: name: Install Docker Compose command: | curl -L https://github.com/docker/compose/releases/download/1.19.0/docker-compose-`uname -s`-`uname -m` > ~/docker-compose chmod +x ~/docker-compose sudo mv ~/docker-compose /usr/local/bin/docker-compose - *install-deps - run: name: Prepare command: | docker-compose up -d sleep 10 - run: name: List containers command: docker ps - run: name: e2e tests command: npm run test:e2e workflows: version: 2 build-and-test: jobs: - build - integration_tests: requires: - build ================================================ FILE: .commitlintrc.json ================================================ { "extends": ["@commitlint/config-angular"], "rules": { "subject-case": [ 2, "always", ["sentence-case", "start-case", "pascal-case", "upper-case", "lower-case"] ], "type-enum": [ 2, "always", [ "build", "chore", "ci", "docs", "feat", "fix", "perf", "refactor", "revert", "style", "test", "sample" ] ] } } ================================================ FILE: .github/ISSUE_TEMPLATE/Bug_report.yml ================================================ name: "\U0001F41B Bug Report" description: "If something isn't working as expected \U0001F914" labels: ["needs triage", "bug"] body: - type: markdown attributes: value: | ## :warning: We use GitHub Issues to track bug reports, feature requests and regressions If you are not sure that your issue is a bug, you could: - use our [Discord community](https://discord.gg/NestJS) - use [StackOverflow using the tag `nestjs`](https://stackoverflow.com/questions/tagged/nestjs) - If it's just a quick question you can ping [our Twitter](https://twitter.com/nestframework) **NOTE:** You don't need to answer questions that you know that aren't relevant. --- - type: checkboxes attributes: label: "Is there an existing issue for this?" description: "Please search [here](./?q=is%3Aissue) to see if an issue already exists for the bug you encountered" options: - label: "I have searched the existing issues" required: true - type: textarea validations: required: true attributes: label: "Current behavior" description: "How the issue manifests?" - type: input validations: required: true attributes: label: "Minimum reproduction code" description: "An URL to some git repository or gist that reproduces this issue. [Wtf is a minimum reproduction?](https://jmcdo29.github.io/wtf-is-a-minimum-reproduction)" placeholder: "https://github.com/..." - type: textarea attributes: label: "Steps to reproduce" description: | How the issue manifests? You could leave this blank if you alread write this in your reproduction code/repo placeholder: | 1. `npm i` 2. `npm start:dev` 3. See error... - type: textarea validations: required: true attributes: label: "Expected behavior" description: "A clear and concise description of what you expected to happend (or code)" - type: markdown attributes: value: | --- - type: input validations: required: true attributes: label: "Package version" description: | Which version of `@nestjs/mongoose` are you using? **Tip**: Make sure that all of yours `@nestjs/*` dependencies are in sync! placeholder: "8.1.3" - type: input attributes: label: "mongoose version" description: "Which version of `mongoose` are you using?" placeholder: "6.0.9" - type: input attributes: label: "NestJS version" description: "Which version of `@nestjs/core` are you using?" placeholder: "8.1.3" - type: input attributes: label: "Node.js version" description: "Which version of Node.js are you using?" placeholder: "14.17.6" - type: checkboxes attributes: label: "In which operating systems have you tested?" options: - label: macOS - label: Windows - label: Linux - type: markdown attributes: value: | --- - type: textarea attributes: label: "Other" description: | Anything else relevant? eg: Logs, OS version, IDE, package manager, etc. **Tip:** You can attach images, recordings or log files by clicking this area to highlight it and then dragging files in ================================================ FILE: .github/ISSUE_TEMPLATE/Feature_request.yml ================================================ name: "\U0001F680 Feature Request" description: "I have a suggestion \U0001F63B!" labels: ["feature"] body: - type: markdown attributes: value: | ## :warning: We use GitHub Issues to track bug reports, feature requests and regressions If you are not sure that your issue is a bug, you could: - use our [Discord community](https://discord.gg/NestJS) - use [StackOverflow using the tag `nestjs`](https://stackoverflow.com/questions/tagged/nestjs) - If it's just a quick question you can ping [our Twitter](https://twitter.com/nestframework) --- - type: checkboxes attributes: label: "Is there an existing issue that is already proposing this?" description: "Please search [here](./?q=is%3Aissue) to see if an issue already exists for the feature you are requesting" options: - label: "I have searched the existing issues" required: true - type: textarea validations: required: true attributes: label: "Is your feature request related to a problem? Please describe it" description: "A clear and concise description of what the problem is" placeholder: | I have an issue when ... - type: textarea validations: required: true attributes: label: "Describe the solution you'd like" description: "A clear and concise description of what you want to happen. Add any considered drawbacks" - type: textarea attributes: label: "Teachability, documentation, adoption, migration strategy" description: "If you can, explain how users will be able to use this and possibly write out a version the docs. Maybe a screenshot or design?" - type: textarea validations: required: true attributes: label: "What is the motivation / use case for changing the behavior?" description: "Describe the motivation or the concrete use case" ================================================ FILE: .github/ISSUE_TEMPLATE/Regression.yml ================================================ name: "\U0001F4A5 Regression" description: "Report an unexpected behavior while upgrading your Nest application!" labels: ["needs triage"] body: - type: markdown attributes: value: | ## :warning: We use GitHub Issues to track bug reports, feature requests and regressions If you are not sure that your issue is a bug, you could: - use our [Discord community](https://discord.gg/NestJS) - use [StackOverflow using the tag `nestjs`](https://stackoverflow.com/questions/tagged/nestjs) - If it's just a quick question you can ping [our Twitter](https://twitter.com/nestframework) **NOTE:** You don't need to answer questions that you know that aren't relevant. --- - type: checkboxes attributes: label: "Did you read the migration guide?" description: "Check out the [migration guide here](https://docs.nestjs.com/migration-guide)!" options: - label: "I have read the whole migration guide" required: false - type: checkboxes attributes: label: "Is there an existing issue that is already proposing this?" description: "Please search [here](./?q=is%3Aissue) to see if an issue already exists for the feature you are requesting" options: - label: "I have searched the existing issues" required: true - type: input attributes: label: "Potential Commit/PR that introduced the regression" description: "If you have time to investigate, what PR/date/version introduced this issue" placeholder: "PR #123 or commit 5b3c4a4" - type: input attributes: label: "Versions" description: "From which version of `@nestjs/mongoose` to which version you are upgrading" placeholder: "8.1.0 -> 8.1.3" - type: textarea validations: required: true attributes: label: "Describe the regression" description: "A clear and concise description of what the regression is" - type: textarea attributes: label: "Minimum reproduction code" description: | Please share a git repo, a gist, or step-by-step instructions. [Wtf is a minimum reproduction?](https://jmcdo29.github.io/wtf-is-a-minimum-reproduction) **Tip:** If you leave a minimum repository, we will understand your issue faster! value: | ```ts ``` - type: textarea validations: required: true attributes: label: "Expected behavior" description: "A clear and concise description of what you expected to happend (or code)" - type: textarea attributes: label: "Other" description: | Anything else relevant? eg: Logs, OS version, IDE, package manager, etc. **Tip:** You can attach images, recordings or log files by clicking this area to highlight it and then dragging files in ================================================ FILE: .github/ISSUE_TEMPLATE/config.yml ================================================ ## To encourage contributors to use issue templates, we don't allow blank issues blank_issues_enabled: false contact_links: - name: "\u2753 Discord Community of NestJS" url: "https://discord.gg/NestJS" about: "Please ask support questions or discuss suggestions/enhancements here." ================================================ FILE: .github/PULL_REQUEST_TEMPLATE.md ================================================ ## PR Checklist Please check if your PR fulfills the following requirements: - [ ] The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md - [ ] Tests for the changes have been added (for bug fixes / features) - [ ] Docs have been added / updated (for bug fixes / features) ## PR Type What kind of change does this PR introduce? - [ ] Bugfix - [ ] Feature - [ ] Code style update (formatting, local variables) - [ ] Refactoring (no functional changes, no api changes) - [ ] Build related changes - [ ] CI related changes - [ ] Other... Please describe: ## What is the current behavior? Issue Number: N/A ## What is the new behavior? ## Does this PR introduce a breaking change? - [ ] Yes - [ ] No ## Other information ================================================ FILE: .gitignore ================================================ # dependencies /node_modules # IDE /.idea /.awcache /.vscode # misc npm-debug.log .DS_Store # tests /test /coverage /.nyc_output # dist dist ================================================ FILE: .husky/.gitignore ================================================ _ ================================================ FILE: .husky/commit-msg ================================================ npx --no-install commitlint --edit $1 ================================================ FILE: .husky/pre-commit ================================================ npx --no-install lint-staged ================================================ FILE: .npmignore ================================================ # source lib index.ts # tests /tests # misc package-lock.json .eslintrc.js tsconfig.json tsconfig.build.json .prettierrc .prettierrc .commitlintrc.json docker-compose.yml .husky/ .github/ .circleci/ renovate.json ================================================ FILE: .prettierrc ================================================ { "trailingComma": "all", "singleQuote": true } ================================================ FILE: .release-it.json ================================================ { "git": { "commitMessage": "chore(): release v${version}" }, "github": { "release": true } } ================================================ FILE: CONTRIBUTING.md ================================================ # Contributing to Nest We would love for you to contribute to Nest and help make it even better than it is today! As a contributor, here are the guidelines we would like you to follow: - [Code of Conduct](#coc) - [Question or Problem?](#question) - [Issues and Bugs](#issue) - [Feature Requests](#feature) - [Submission Guidelines](#submit) - [Coding Rules](#rules) - [Commit Message Guidelines](#commit) ## Got a Question or Problem? **Do not open issues for general support questions as we want to keep GitHub issues for bug reports and feature requests.** You've got much better chances of getting your question answered on [Stack Overflow](https://stackoverflow.com/questions/tagged/nestjs) where the questions should be tagged with tag `nestjs`. Stack Overflow is a much better place to ask questions since: - questions and answers stay available for public viewing so your question / answer might help someone else - Stack Overflow's voting system assures that the best answers are prominently visible. To save your and our time, we will systematically close all issues that are requests for general support and redirect people to Stack Overflow. If you would like to chat about the question in real-time, you can reach out via [our discord channel][discord]. ## Found a Bug? If you find a bug in the source code, you can help us by [submitting an issue](#submit-issue) to our [GitHub Repository][github]. Even better, you can [submit a Pull Request](#submit-pr) with a fix. ## Missing a Feature? You can *request* a new feature by [submitting an issue](#submit-issue) to our GitHub Repository. If you would like to *implement* a new feature, please submit an issue with a proposal for your work first, to be sure that we can use it. Please consider what kind of change it is: * For a **Major Feature**, first open an issue and outline your proposal so that it can be discussed. This will also allow us to better coordinate our efforts, prevent duplication of work, and help you to craft the change so that it is successfully accepted into the project. For your issue name, please prefix your proposal with `[discussion]`, for example "[discussion]: your feature idea". * **Small Features** can be crafted and directly [submitted as a Pull Request](#submit-pr). ## Submission Guidelines ### Submitting an Issue Before you submit an issue, please search the issue tracker, maybe an issue for your problem already exists and the discussion might inform you of workarounds readily available. We want to fix all the issues as soon as possible, but before fixing a bug we need to reproduce and confirm it. In order to reproduce bugs we will systematically ask you to provide a minimal reproduction scenario using a repository or [Gist](https://gist.github.com/). Having a live, reproducible scenario gives us wealth of important information without going back & forth to you with additional questions like: - version of NestJS used - 3rd-party libraries and their versions - and most importantly - a use-case that fails Unfortunately, we are not able to investigate / fix bugs without a minimal reproduction, so if we don't hear back from you we are going to close an issue that don't have enough info to be reproduced. You can file new issues by filling out our [new issue form](https://github.com/nestjs/nest/issues/new). ### Submitting a Pull Request (PR) Before you submit your Pull Request (PR) consider the following guidelines: 1. Search [GitHub](https://github.com/nestjs/nest/pulls) for an open or closed PR that relates to your submission. You don't want to duplicate effort. 1. Fork the nestjs/nest repo. 1. Make your changes in a new git branch: ```shell git checkout -b my-fix-branch master ``` 1. Create your patch, **including appropriate test cases**. 1. Follow our [Coding Rules](#rules). 1. Run the full Nest test suite, as described in the [developer documentation][dev-doc], and ensure that all tests pass. 1. Commit your changes using a descriptive commit message that follows our [commit message conventions](#commit). Adherence to these conventions is necessary because release notes are automatically generated from these messages. ```shell git commit -a ``` Note: the optional commit `-a` command line option will automatically "add" and "rm" edited files. 1. Push your branch to GitHub: ```shell git push origin my-fix-branch ``` 1. In GitHub, send a pull request to `nestjs:master`. * If we suggest changes then: * Make the required updates. * Re-run the Nest test suites to ensure tests are still passing. * Rebase your branch and force push to your GitHub repository (this will update your Pull Request): ```shell git rebase master -i git push -f ``` That's it! Thank you for your contribution! #### After your pull request is merged After your pull request is merged, you can safely delete your branch and pull the changes from the main (upstream) repository: * Delete the remote branch on GitHub either through the GitHub web UI or your local shell as follows: ```shell git push origin --delete my-fix-branch ``` * Check out the master branch: ```shell git checkout master -f ``` * Delete the local branch: ```shell git branch -D my-fix-branch ``` * Update your master with the latest upstream version: ```shell git pull --ff upstream master ``` ## Coding Rules To ensure consistency throughout the source code, keep these rules in mind as you are working: * All features or bug fixes **must be tested** by one or more specs (unit-tests). * We follow [Google's JavaScript Style Guide][js-style-guide], but wrap all code at **100 characters**. An automated formatter is available, see [DEVELOPER.md](docs/DEVELOPER.md#clang-format). ## Commit Message Guidelines We have very precise rules over how our git commit messages can be formatted. This leads to **more readable messages** that are easy to follow when looking through the **project history**. But also, we use the git commit messages to **generate the Nest change log**. ### Commit Message Format Each commit message consists of a **header**, a **body** and a **footer**. The header has a special format that includes a **type**, a **scope** and a **subject**: ``` ():