Skip to content

Update typo in readme #26

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.

Sign up for GitHub

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

Open
domengabrovsek wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update typo in readme #26

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion backend/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ The API you are building supports CRUD operations on `user` and `event` entities
- A user can have multiple events that, when applied in the order of their creation, will generate the current user consent status.
- A user accepts only one required field (`email`) that must be a valid email address and unique. If any of the requirements are not satisfied, the API must return a 422 response.
- Consent IDs can be one of the following: `email_notifications` or `sms_notifications`.
- Consent change events can only be read and created, not update or deleted.
- Consent change events can only be read and created, not updated or deleted.
- A consent change event belongs to a single user.

To keep the challenge as short as possible the mandatory routes and methods are the following:
Expand Down