Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello, I started using Ink and really like it.
There are several things which have been bugging me in the documentation though, and the most confusing one is the inconsistent indentations. Now I know they hold no syntactic value, but many indentations are inconsistent within a single example, and across the whole text. This makes it harder to follow and get an idea for the style of the language.
This pull request does two things:
This is a feature from GitHub Flavoured Markdown, but it’s quite ubiquitous, and was even present in one example from this document. I also checked that it didn’t mess up Inky’s internal documentation—which appears outdated, by the way.
One thing to consider is that your examples use tabs a lot, which have some advantages, but don’t work nicely everywhere. Since GH uses 8-column tabs, some indentation which are meant for 2- or 4-column look broken.
I’m writing a tool that automatically indents Ink files, so while I’m at it, I could reindent everything using spaces without much effort if you’d like.