Generate contracts with define-jsexpr-mapping #1

Open
opened 2020-10-04 10:54:49 +00:00 by epi · 3 comments
Owner

Currently the define-jsexpr-mapping macro produces only getters for a JSON object. It would be an improvement to make it generate contracts as well.

Currently the `define-jsexpr-mapping` macro produces only getters for a JSON object. It would be an improvement to make it generate contracts as well.
Author
Owner
  • Each field should have a contract associated with it (any/c by default?)
  • Each getter should be wrapped in contracts
  • All API methods should be protected by contracts
- Each field should have a contract associated with it (`any/c` by default?) - Each getter should be wrapped in contracts - All API methods should be protected by contracts
Author
Owner

Contracts on the JSON objects can be quite complicated, because certain fields could be omitted.
For example, in_reply_to field in the Status object.

Contracts on the JSON objects can be quite complicated, because certain fields could be omitted. For example, `in_reply_to` field in the `Status` object.
Author
Owner

Note to self: there is some hacking in the contracts branch.

Note to self: there is some hacking in the `contracts` branch.
Sign in to join this conversation.
No labels
wish
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: epi/tapris2#1
No description provided.