search

Ssentiago / obsidian-openapi-renderer

Integrate OpenAPI specification management into Obsidian with features for version control, visualization, editing, and easy navigation of API specs.
Apache License 2.0
6 stars 1 forks source link

Anchor Links for Routes in YAML Files #14

Open Darkrogua opened 1 month ago

Darkrogua commented 1 month ago

Hello, thanks for the plugin! As I understand it, there is currently no way to create anchor links to specific routes in a YAML file when viewing OpenAPI specs. This would be really useful for navigating large files, especially when there are many endpoints listed.

Is there any plan to support this feature, or would you consider adding it? It would help a lot with referencing specific API routes directly from other notes in Obsidian.

Ssentiago commented 1 month ago

Hello, thanks for the plugin! As I understand it, there is currently no way to create anchor links to specific routes in a YAML file when viewing OpenAPI specs. This would be really useful for navigating large files, especially when there are many endpoints listed.

Is there any plan to support this feature, or would you consider adding it? It would help a lot with referencing specific API routes directly from other notes in Obsidian.

Hello! Do you mean $ref links and their management?

Darkrogua commented 1 month ago

Hello! Do you mean $ref links and their management?

No, I don't mean $ref links. I'm asking about the ability to create anchor links (similar to HTML anchors) to specific routes or sections in a YAML file. This would allow for easier navigation within large OpenAPI specs by referencing a particular API route directly, rather than managing schema references through $ref.

Ssentiago commented 1 month ago

Hello! Do you mean $ref links and their management?

No, I don't mean $ref links. I'm asking about the ability to create anchor links (similar to HTML anchors) to specific routes or sections in a YAML file. This would allow for easier navigation within large OpenAPI specs by referencing a particular API route directly, rather than managing schema references through $ref.

Why not? It looks like an interesting feature. I'll think about it, thanks for leaving the idea.