Skip to content

issue #19 verwerken in Design rules #2

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

Merged
jasperroes merged 1 commit into from
Mar 5, 2020
Merged

issue #19 verwerken in Design rules #2

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
6 changes: 6 additions & 0 deletions Designrules v1.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,6 +83,12 @@ Here, the *Keep It Simple Stupid* (KISS) rule is applicable. Although grammatica

> [API principle: Use plural nouns to indicate resources](#api-05)

### Naming convention

The API Design rules do not specify naming conventions for API's, inspiration for naming an API can be found at:
- Service names: https://cloud.google.com/apis/design/naming_convention#service_names
- Interface names: https://cloud.google.com/apis/design/naming_convention#interface_names

### How to deal with relations?

If a relation can only exist in the context of another resource (1 to n relation), then the dependent resource (child) can only be retrieved through the parent. The next example explains this. A status belongs to one application. Statuses can be retrieved through the endpoint `/aanvragen`:
Expand Down