-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add ascii art #16
add ascii art #16
Conversation
@@ -93,6 +93,62 @@ Using the token bearer model ([RFC6750](https://datatracker.ietf.org/doc/html/rf | |||
# Example Request Flow | |||
For a diagram, please see: https://github.com/bgp/autopeer/blob/main/README.md#sequence-diagram | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As per
https://github.com/cabo/kramdown-rfc/blob/master/examples/stupid-s.mkd
You should "box" this diagram with
~~~~~~~~~~
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Ichabond oh, good catch, thanks. I guess I should do a local install and check how the rendering works.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can check the build artifacts here, too: https://github.com/bgp/draft-ietf-peering-api/actions/runs/7659907136
Let's see if it works with the ~~~?
Looks nice to me! Thanks for putting it together. Fine by me to merge once it renders correctly in the artifact. |
resolved merge conflicts |
I think this fixes the formatting? Just based on the example in https://github.com/cabo/kramdown-rfc/blob/master/examples/stupid-s.mkd?plain=1
Format diagram for draft
Add ascii representations of the mermaid docs. They are hand made and I'm not sure it makes sense to diagram more than the Auth loop part.
It does look like we can have the svg rendered for the html views [0], using our github actions template [1]. Should we look at adding both or leave it as is for the first version?
[0] https://authors.ietf.org/diagrams
[1] https://github.com/cabo/kramdown-rfc/wiki/SVG