doc: fix syntax problems in task list
This commit is contained in:
@@ -46,6 +46,7 @@ export interface CommentClaim extends ClaimObject {
|
|||||||
text: string;
|
text: string;
|
||||||
parentItem: { identifier: string };
|
parentItem: { identifier: string };
|
||||||
}
|
}
|
||||||
|
```
|
||||||
|
|
||||||
### 6. Authentication & Authorization
|
### 6. Authentication & Authorization
|
||||||
- [ ] Emojis require valid JWT authentication (like other claims)
|
- [ ] Emojis require valid JWT authentication (like other claims)
|
||||||
@@ -91,10 +92,10 @@ export interface CommentClaim extends ClaimObject {
|
|||||||
## Implementation Notes
|
## Implementation Notes
|
||||||
|
|
||||||
This design follows the existing Endorser Server patterns:
|
This design follows the existing Endorser Server patterns:
|
||||||
- [ ] Reuses the proven JWT claim submission system
|
- Reuses the proven JWT claim submission system
|
||||||
- [ ] Follows the established database and API patterns
|
- Follows the established database and API patterns
|
||||||
- [ ] Maintains consistency with existing visibility and authentication rules
|
- Maintains consistency with existing visibility and authentication rules
|
||||||
- [ ] Supports the distributed/P2P vision by storing emojis as signed claims
|
- Supports the distributed/P2P vision by storing emojis as signed claims
|
||||||
|
|
||||||
The emoji feature will integrate seamlessly with the existing GiveAction display system, showing emoji counts alongside other give information and providing a separate endpoint for detailed emoji retrieval when users want to see who reacted and with what emojis.
|
The emoji feature will integrate seamlessly with the existing GiveAction display system, showing emoji counts alongside other give information and providing a separate endpoint for detailed emoji retrieval when users want to see who reacted and with what emojis.
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user