todos from eric regarding new api playground

[BelfordZ]

• port over docs from JSON-RPC API docs and remove the former. #816
  • primary / secondary tagging to figure out grouping the links by tags #817
• filter by tags / make tags clickable #818
• hotkeys
  • hotkey to clear #826
  • hotkey to paste example in #827
• spacing between params in interactive method (h3s) #819
• json-schema-viewer contrast ratios on the types #820
• json-schema-viewer array of: should make it clear where the border of the following type is #821
• interactive method button alignment for objects is messed #822
• interactive method buttons need outlines when they are selected/highlighted #823
• clicking a method link makes the sidebar scroll up #824
• interactive methods checkboxes are not the nicest lookin #825
• add a way to autocomplete / autofill the result of one method to the params of another (eth_subscribe and eth_unsubscribe) #830

[httpJunkie]

Can the Playground remember the return result from eth_subscribe and
ensure it is populated on the eth_unsubscribe page after a subscribe request?

[BelfordZ]

yep! this would be something we could have working with the concept of links

If we implement links, in the docs we can remember the results from previous calls, and give suggestions for future params based on what you've seen already. Ty for the suggestion, its a great one!

Ive added that to the list!