Skip to content
This repository has been archived by the owner on Dec 12, 2024. It is now read-only.

RFC-0001 Standard tbDEX API Design (APID) Document v0.1.0 #57

Merged
merged 7 commits into from
Jun 28, 2024

Conversation

KendallWeihe
Copy link
Contributor

@KendallWeihe KendallWeihe commented Jun 19, 2024

See RFC-0001 for full description.

@KendallWeihe KendallWeihe changed the title Draft: RFC-0001 Standard tbDEX API Design (APID) Document v0.1.0 RFC-0001 Standard tbDEX API Design (APID) Document v0.1.0 Jun 28, 2024
@KendallWeihe KendallWeihe marked this pull request as ready for review June 28, 2024 03:13

> [!WARNING]
>
> Snake vs camel casing is inconsistent
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is because the spec or rust binding stuff?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just cause move fast


> [!WARNING]
>
> We need to define `JsonNode`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I Will think about this... there must be a idiomatic way

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right now I'm referencing the Custom DSL over in web5-rs, even though we're inside tbdex-rs. Basically I think we just need to add the concept of a JSON Object type to the Custom DSL and then update this APID and the web5-rs APID to use that new syntax.

Copy link
Contributor

@nitro-neal nitro-neal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice 🔥

@KendallWeihe KendallWeihe merged commit f9837ad into main Jun 28, 2024
6 checks passed
@KendallWeihe KendallWeihe deleted the kendall/rfc-0001 branch June 28, 2024 17:38
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants