Skip to content

docs: add missing div to seperate bad and good examples #2540

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Oct 30, 2023
Merged

docs: add missing div to seperate bad and good examples #2540

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d70a71d
Update rules-recommended.md
JeremieLitzler Oct 18, 2023
c79c49a
Merge pull request #1 from JeremieLitzler/patch-1
JeremieLitzler Oct 18, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions src/style-guide/rules-recommended.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,8 +127,8 @@ This is the default order we recommend for component options. They're split into

When components begin to feel cramped or difficult to read, adding spaces between multi-line properties can make them easier to skim again. In some editors, such as Vim, formatting options like this can also make them easier to navigate with the keyboard.

<div class="style-example style-example-good">
<h3>Good</h3>
<div class="style-example style-example-bad">
<h3>Bad</h3>

```js
props: {
Expand Down Expand Up @@ -156,6 +156,10 @@ computed: {
}
}
```
</div>

<div class="style-example style-example-good">
<h3>Good</h3>

```js
// No spaces are also fine, as long as the component
Expand Down