feat: ✨ initial user application

[zhumeisongsong]

Closes #4

Summary by CodeRabbit

Summary by CodeRabbit

Release Notes

• New Features

  • Introduced a new end-to-end testing configuration for the users application, including Jest and ESLint setups.
  • Added a basic API with a GET endpoint that returns a greeting message.

• Bug Fixes

  • Updated Jest configuration to ensure consistent testing across applications.

• Documentation

  • Added TypeScript configuration files to enhance type safety and interoperability.

• Tests

  • Implemented new test suites for the AppController and AppService to validate API functionality.
  • Enhanced testing coverage for the API's GET endpoint.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request introduces several configuration files and test setups for the users-application and users-application-e2e applications. New ESLint and Jest configuration files are created for both applications to standardize linting and testing practices. Additionally, global setup and teardown scripts for end-to-end testing are implemented, along with a test setup for Axios. The AppController and AppService classes are added to the users-application, accompanied by corresponding test suites to validate their functionality.

Changes

File Path	Change Summary
apps/users-application-e2e/eslint.config.js	New ESLint configuration file that extends base rules.
apps/users-application-e2e/jest.config.ts	New Jest configuration file with setup and teardown scripts for testing.
apps/users-application-e2e/project.json	New project configuration defining e2e testing targets and dependencies.
apps/users-application-e2e/src/support/global-setup.ts	New global setup script for e2e testing environment.
apps/users-application-e2e/src/support/global-teardown.ts	New global teardown script for e2e testing environment.
apps/users-application-e2e/src/support/test-setup.ts	New test setup module for configuring Axios HTTP client.
apps/users-application-e2e/src/users-application/users-application.spec.ts	New test suite for validating API GET request.
apps/users-application-e2e/tsconfig.json	New TypeScript configuration extending from a base config.
apps/users-application-e2e/tsconfig.spec.json	New TypeScript configuration for e2e tests.
apps/users-application/eslint.config.js	New ESLint configuration file that extends base rules.
apps/users-application/jest.config.ts	New Jest configuration file for the users application.
apps/users-application/project.json	New project configuration defining application schema and serve target.
apps/users-application/src/app/app.controller.spec.ts	New test suite for AppController.
apps/users-application/src/app/app.controller.ts	New AppController class with a GET method.
apps/users-application/src/app/app.module.ts	New AppModule class defining the application structure.
apps/users-application/src/app/app.service.spec.ts	New test suite for AppService.
apps/users-application/src/app/app.service.ts	New AppService class with a method returning a message.
apps/users-application/src/main.ts	New entry point for the NestJS application with server initialization.
apps/users-application/tsconfig.app.json	New TypeScript configuration for the users application.
apps/users-application/tsconfig.json	New TypeScript configuration extending from a base config.
apps/users-application/tsconfig.spec.json	New TypeScript configuration for the users application tests.
apps/users-application/webpack.config.js	New Webpack configuration for the users application.
nx.json	Updated Jest plugin configuration to exclude additional paths from testing.

Possibly related PRs

• feat: ✨ initial gateway app #1: The introduction of ESLint configuration files in this PR parallels similar changes made in the gateway application, indicating a consistent approach to linting across applications.
• feat: ✨ add applicaiton config #7: This PR's changes to configuration files may relate to the overall project structure, which is also addressed in another PR that adds application configuration.
• feat: ✨ Initial graphql federation: users application #14: The focus on application structure and configuration aligns with the introduction of a new application in this PR.
• feat: ✨ Federated gateway #18: Changes to configuration files may connect with the federated architecture discussed in this PR.
• refactor: ♻️ Create a ConfigModule that exposes a ConfigService which loads the appropriate .env file #28: The introduction of configuration files may relate to the new ConfigModule introduced in this PR, which also deals with environment configurations.
• refactor: ♻️ import User from @user/domain #31: Changes regarding configuration files may relate to the refactoring of user-related imports in this PR.
• refactor: ♻️ Move prompt related entities to @prompt/domain #32: The focus on configuration files may connect with the refactoring of prompt-related entities in this PR.
• feat: ✨ GetUserUsecase #36: Changes to configuration files may relate to the introduction of a new use case for user retrieval in this PR.
• feat: ✨ add @shared/infrastructure-mongoose #42: Changes to configuration files may connect with the addition of the shared infrastructure for Mongoose in this PR.
• refactor: ♻️ rename users-application to users #43: Changes to project structure and naming conventions may relate to the renaming of the users application in this PR.
• feat: ✨ add users/presentation lib #46: The focus on configuration files may connect with the introduction of a new presentation library for users in this PR.

🐰 In the meadow, changes bloom,
New configs chase away the gloom.
With tests and setups, all in line,
The users app will surely shine!
Hooray for code, let’s hop and play,
In our joyful, rabbit way! 🐇✨

Warning

Rate limit exceeded

@github-actions[bot] has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 29 minutes and 28 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between d744cff and ea43646.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[zhumeisongsong]

Merged without AI review since initial app only

[github-actions]

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀