-
Notifications
You must be signed in to change notification settings - Fork 533
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
Move code out of MD files #126
Comments
I was looking into this today and sadly github is still working on securing markup includes github/markup#172 (comment) and it is currently not possible to do without pre-processing. |
Checking: no change on the github side of things. This is a generic ticket with possibly a different solution, so if somebody has a low-overhead working principle to point at then we should definitely try it out. |
I think we should just link to the example files or the spec classes (now with Java they have their own files). |
@reactive-streams @viktorklang so are we planning on doing something with this now? |
I think this will stay as a "nice-to-have". |
Sounds good to me. |
I don't think there's enough need to warrant this Issue. If someone disagrees, please reopen. |
This is follow-up from PR #125:
@viktorklang wrote:
(...) what I meant was that I think that sample code should live in compiled files, so that we can catch when it needs to be updated. As such I think all code should be moved out of .mds and put into files and then either imported automatically into the .mds or be linked from the .mds.
The text was updated successfully, but these errors were encountered: