Skip to content
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.

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

doc: remove todos, add note on URLs #4

Merged
merged 4 commits into from
Aug 7, 2024

Conversation

aatifsyed
Copy link

@aatifsyed aatifsyed changed the title doc: remove todos doc: remove todos, add note on URLs Jul 22, 2024
Copy link
Member

@ansermino ansermino left a comment

Choose a reason for hiding this comment

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

For the v0/v1 APIs - I recall we were going to define the path that the API should be served one, whereas these changes seem to only specify which part of the Lotus API we are referencing. Am I remembering that correctly?

@@ -49,6 +49,9 @@ Additionally, by establishing a specification we seek to establish a greater res
Using the OpenRPC specification format we define several groups of methods. These methods are defined in the OpenRPC specification found here: https://github.com/ChainSafe/filecoin-openrpc-spec. A list of the methods is included below for posterity.

All methods are reproduced identically to their present implementation in Lotus 1.26.1.
Note that Lotus hosts two different API's at HTTP paths [`/rpc/v0`](https://github.com/filecoin-project/lotus/blob/v1.28.0-rc5/documentation/en/api-v0-methods.md) and [`/rpc/v1`](https://github.com/filecoin-project/lotus/blob/v1.28.0-rc5/documentation/en/api-v1-unstable-methods.md),
with the latter being marked as _unstable_.
This document aims to specify the _latest_ API version (in this case, `v1`) and breaking changes will be negotiated through further FIPs.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
This document aims to specify the _latest_ API version (in this case, `v1`) and breaking changes will be negotiated through further FIPs.
This document aims to specify the `V1` API.

"latest" and "version" are a bit confusing here as the version of Lotus is mentioned just before. Additional changes via FIP is defined below.

FIPS/fip-common_node_api.md Outdated Show resolved Hide resolved
@aatifsyed
Copy link
Author

For the v0/v1 APIs - I recall we were going to define the path that the API should be served one, whereas these changes seem to only specify which part of the Lotus API we are referencing. Am I remembering that correctly?

Yes, we floated the idea of e.g a rpc/common-node-api/v1 HTTP path early on.
But we then decided to be "purely descriptive", deferring the following:

  • URL paths
  • API versioning

I've written this section from that descriptivist PoV - does that match your expectation?

@aatifsyed aatifsyed merged commit b6ea9a7 into ansermino/rpc-api Aug 7, 2024
1 check passed
@aatifsyed aatifsyed deleted the aatifsyed/common-node-api branch August 7, 2024 13:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants