Skip to content
This repository was archived by the owner on Feb 27, 2021. It is now read-only.
This repository was archived by the owner on Feb 27, 2021. It is now read-only.

Linking / url API overhaul #382

@BelfordZ

Description

@BelfordZ

Is your feature request related to a problem? Please describe.
The current linking scheme has a mixed use of url params as well as path-encoded vars. Specifically, you can set the network by attaching a param at the end ?network=mainnet. Further, you can combine this with block by hash, by number, etcetc.

Describe the solution you'd like
The urls should be constructed as follows:

/:network/:contentTypeName/:contentTypeQueryParam(s)

No nesting at the moment.

Describe alternatives you've considered

future considerations:

  • url to get a block with given transaction
  • url to get a block/tx by hash from any network

Additional context

Deep linking api is important for a lot of users. however, with this change, savings pre-renderings becomes a lot easier, and we can likely improve our SEO tremendously by doing this.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions