As a writer of an open-rpc document, I don't want to have to repeat the same values throughout the document.
ex:
"I have to set paramStructure in every method because my API is by-name only""Theres no way to refer to a group of errors, I have to ref the same errors in every method"
etc etc
Solutions considered:
Add solutions on an as-needed basis. When someone wants param structure on the root, add it. When someone whats Error groups, add it.
Add the ability to set defaults for main data structures, placed in under a root key named defaults. This would work similar to components, though it would have specific meaning to tooling developers to observe.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
As a writer of an open-rpc document, I don't want to have to repeat the same values throughout the document. ex:
"I have to set paramStructure in every method because my API is by-name only" "Theres no way to refer to a group of errors, I have to ref the same errors in every method"
etc etc
Solutions considered:
defaults
. This would work similar to components, though it would have specific meaning to tooling developers to observe.