Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Juno Onboarding Ticket #152

Open
8 tasks
UZ9 opened this issue Jan 24, 2025 · 0 comments
Open
8 tasks

Juno Onboarding Ticket #152

UZ9 opened this issue Jan 24, 2025 · 0 comments

Comments

@UZ9
Copy link
Contributor

UZ9 commented Jan 24, 2025

This is a dummy ticket intended to help new developers of Juno get more accustomed to its codebase structure.

You will be creating a new counter module in the db-service, and in the process learning the docker setup, prisma migrations, protobuf integration, and our end-to-end testing.

Requirements & Criteria

  • Follow the README instructions to set up the Juno repository and successfully run the api-gateway e2e tests
  • Create a new prisma model Counter with a string identifier (id) and int value. For all of your methods implemented below, an ID parameter will be specified.
  • Create a new counter.proto with the following calls available: incrementCounter, decrementCounter, resetCounter, getCounter. These should all have their respective requests (e.g. IncrementCounterRequest)
  • Create a new "counter" module in db-service under the modules folder. For reference, take a look at the NestJS documentation on modules and how other existing modules are handled.
  • Create the following methods within the module: incrementCounter, decrementCounter, resetCounter, getCounter. Each should perform their respective name on the single counter you defined in prisma, using your defined proto definitions.
  • Create a new "counter" module in api-gateway to allow your counter to be accessible via the API gateway. The module is responsible for calling the respective methods on the db-service.

Testing

  • Create a new counter.e2e-spec.ts within db-service with at least 1 test for each method. For reference, take a look at other e2e-spec files within the same folder.
  • Create a new counter.e2e-spec.ts within api-gateway with at least 1 test for each method (api-gateway implementation, not db-service). For reference, take a look at other e2e-spec files within the same folder.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant