forked from Haldis/menus
Tabs don't work at all for alignment
I had forgotten this fact when I wrote the old version of this paragraph.
This commit is contained in:
parent
1c3781744a
commit
acadf9d6b4
1 changed files with 5 additions and 5 deletions
10
README.md
10
README.md
|
@ -8,10 +8,10 @@ repository](https://git.zeus.gent/haldis/haldis/-/tree/master/etc). For VSCode t
|
|||
in the standard repository.
|
||||
|
||||
## Indentation
|
||||
Indentation at the beginning of the line requires hard **tabs**. Spaces will not work.
|
||||
Indentation at the beginning of the line requires hard **tabs** (spaces will not work).
|
||||
|
||||
For alignment (putting things in the same column between lines) spaces are allowed. Example (`↦`
|
||||
for tab and `·` for space):
|
||||
For alignment (putting things in the same column between lines) **spaces** are required (tabs will
|
||||
not work). Example (`↦` for tab and `·` for space):
|
||||
```
|
||||
dish·fries:·Frietjes
|
||||
↦ single_choice size:·Formaat
|
||||
|
@ -101,14 +101,14 @@ dish dishid: Name -- This is a description € 3
|
|||
|
||||
**Note:** Only the `{no_text}` tag is supported at this moment. You can ignore other tags for now.
|
||||
|
||||
You can add tags after ` :: `. Tags are `{identifier}`. You can use tags to attach more information
|
||||
You can add tags after ` `. Tags are `{identifier}`. You can use tags to attach more information
|
||||
about a dish or option in a structured way. For example: `{has_meat}` signals to vegetarians that
|
||||
they should avoid this.
|
||||
|
||||
The order is always id, name, description, tags, price (not all have to be present of course).
|
||||
|
||||
```hlds
|
||||
dish dishid: Name -- This is a description :: {has_meat} € 3
|
||||
dish dishid: Name -- This is a description {has_meat} € 3
|
||||
```
|
||||
|
||||
The `{no_text}` tag signals that an option is not to be shown in a dish's description. This is
|
||||
|
|
Loading…
Reference in a new issue