mirror of
https://github.com/cadmium-im/cadmium-docs-legacy.git
synced 2024-11-09 20:21:03 +00:00
Fix CEDF
This commit is contained in:
parent
f209420ee0
commit
0688f8849d
@ -8,8 +8,9 @@ This extension is intended for logging into user account on a server by username
|
|||||||
|
|
||||||
- `profile:login`
|
- `profile:login`
|
||||||
|
|
||||||
## Error Identifiers
|
## Errors
|
||||||
|
|
||||||
|
- Ratelimit system: enabled
|
||||||
- `invalid_creds`: user ID/password isn't valid
|
- `invalid_creds`: user ID/password isn't valid
|
||||||
|
|
||||||
## Use cases
|
## Use cases
|
||||||
@ -60,7 +61,7 @@ This extension is intended for logging into user account on a server by username
|
|||||||
|
|
||||||
## Business Rules
|
## Business Rules
|
||||||
|
|
||||||
- Ratelimit system: enabled
|
None.
|
||||||
|
|
||||||
## JSON Schema
|
## JSON Schema
|
||||||
|
|
||||||
|
@ -10,6 +10,7 @@ This extension is intended for creating user accounts on a server
|
|||||||
|
|
||||||
## Error identifiers
|
## Error identifiers
|
||||||
|
|
||||||
|
- Ratelimit system: enabled
|
||||||
- `id_exists`: username/third party ID already taken
|
- `id_exists`: username/third party ID already taken
|
||||||
- `reg_disabled`: registration isn't allowed on a server
|
- `reg_disabled`: registration isn't allowed on a server
|
||||||
|
|
||||||
@ -66,7 +67,7 @@ This extension is intended for creating user accounts on a server
|
|||||||
|
|
||||||
## Business Rules
|
## Business Rules
|
||||||
|
|
||||||
- Ratelimit system: enabled
|
None.
|
||||||
|
|
||||||
## JSON Schema
|
## JSON Schema
|
||||||
|
|
||||||
|
@ -22,7 +22,7 @@ When writing use cases and the associated protocols, make sure to:
|
|||||||
* Describe the expected behavior of Cadmium clients, servers, and components when using this protocol.
|
* Describe the expected behavior of Cadmium clients, servers, and components when using this protocol.
|
||||||
* Include lots of protocol examples.
|
* Include lots of protocol examples.
|
||||||
|
|
||||||
*Example 1. An Example from Shakespeare*
|
*Example 1. An Example from Shakespeare*:
|
||||||
|
|
||||||
```json
|
```json
|
||||||
{
|
{
|
||||||
@ -36,13 +36,13 @@ When writing use cases and the associated protocols, make sure to:
|
|||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
## Error Codes
|
## Errors
|
||||||
|
|
||||||
If your proposal defines a number of error and status codes, it is a good idea to include a table of all the codes defined in your document.
|
If your proposal defines a number of error and error identifiers, it is a good idea to include a table of all the identifiers defined in your document.
|
||||||
|
|
||||||
## Business Rules
|
## Business Rules
|
||||||
|
|
||||||
You may want to include a section describing various business rules (essentially, a variety of MUSTs, SHOULDs, and MAYs regarding application behavior). This is not required but can be helpful to implementers.
|
You may want to include a section describing various business rules (essentially, a variety of MUSTs, SHOULDs, and MAYs regarding application behavior). This section is not required but can be helpful to implementers.
|
||||||
|
|
||||||
## Implementation Notes
|
## Implementation Notes
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user