9 Commits (aa40b42cd025765d3f53253d6cbcbc46c0b47930)

Author	SHA1	Message	Date
Max Alekseenko	706de850f4	more scripts optimization	5 years ago
Ayrat Badykov	02eb01ecb5	fix try it out section	5 years ago
saneery	b479aae84a	Set not full path to api on ajax queries	5 years ago
saneery	0a647d0acb	Remove schema from api url	5 years ago
saneery	c4ca6ba2b5	Fix error of url in API page	5 years ago
Ryan Arthur	1f5d183d8d	More loading spinners	6 years ago
Luke Imhoff	613bf24c93	requuest -> request	6 years ago
Luke Imhoff	072f05f320	commmand -> command	6 years ago
Andrew Cravenho	cf75276fe8	Change explorer_web to block_scout_web	6 years ago
Sebastian Abondano	4e9dcced6c	Adds API docs page with 'try it' UI ... Why: * We'd like to provide an API documentation page with a 'Try it out' UI for the API. We first considered using Swagger for this but when we looked into it we realized it didn't fit our needs. It doesn't fit our needs because Swagger is an API specification and the Swagger UI is built for this specification. The Etherscan-compatible API we're building doesn't meet the Swagger specification (name was changed to OpenAPI on the latest version) so we can't easily use Swagger tools to document our API. * Issue link: https://github.com/poanetwork/poa-explorer/issues/454 This change addresses the need by: * Adding API documentation page with 'Try it out' UI at `/api_docs`. The API documentation data is defined within `ExplorerWeb.Etherscan` and rendered by Phoenix templates, with partial templates for 'module cards', 'action tiles', and 'model tables'. The `Try it out` UI is powered by the `try_api.js` file, which shows/hides the 'Try it out' UI as needed and provides support for testing the API from the docs page.	6 years ago