You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As requested by @jexp, it would be great to be able to convert any AsciiDoc files to browser guide.
We could add a new route, for instance /browser-guide, that takes a source parameter:
GET https://portal.graphgist.org/browser-guide?source=https://raw.githubusercontent.com/neo4j-contrib/sandbox-code-updater/main/README.adoc
The above route will load the AsciiDoc file from the source parameter (in this case GitHub), convert it to a browser guide and return HTML.
If we want to get fancy, we could support other URL format for GitHub (or other well-know providers), for instance:
As requested by @jexp, it would be great to be able to convert any AsciiDoc files to browser guide.
We could add a new route, for instance
/browser-guide
, that takes asource
parameter:The above route will load the AsciiDoc file from the
source
parameter (in this case GitHub), convert it to a browser guide and return HTML.If we want to get fancy, we could support other URL format for GitHub (or other well-know providers), for instance:
Or even include the source in the route:
We could then use this URL in the Neo4j browser:
The text was updated successfully, but these errors were encountered: