Enforce Markdown ordered list marker style (#28174)

This commit is contained in:
Franck Nijhof 2023-07-11 15:35:11 +02:00 committed by GitHub
parent 1170f37732
commit eaa3fb7033
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 29 additions and 8 deletions

View File

@ -15,6 +15,7 @@ var remarkrc = {
["remark-lint-heading-increment"], ["remark-lint-heading-increment"],
["remark-lint-heading-style", "atx"], ["remark-lint-heading-style", "atx"],
["remark-lint-unordered-list-marker-style", "-"], ["remark-lint-unordered-list-marker-style", "-"],
["remark-lint-ordered-list-marker-style", "."],
[ [
"remark-lint-prohibited-strings", "remark-lint-prohibited-strings",
[ [

19
package-lock.json generated
View File

@ -15,6 +15,7 @@
"remark-lint-heading-increment": "^3.1.2", "remark-lint-heading-increment": "^3.1.2",
"remark-lint-heading-style": "^3.1.2", "remark-lint-heading-style": "^3.1.2",
"remark-lint-no-shell-dollars": "^3.1.2", "remark-lint-no-shell-dollars": "^3.1.2",
"remark-lint-ordered-list-marker-style": "^3.1.2",
"remark-lint-prohibited-strings": "^3.1.0", "remark-lint-prohibited-strings": "^3.1.0",
"remark-lint-unordered-list-marker-style": "^3.1.2", "remark-lint-unordered-list-marker-style": "^3.1.2",
"remark-stringify": "^10.0.3", "remark-stringify": "^10.0.3",
@ -3590,6 +3591,24 @@
"url": "https://opencollective.com/unified" "url": "https://opencollective.com/unified"
} }
}, },
"node_modules/remark-lint-ordered-list-marker-style": {
"version": "3.1.2",
"resolved": "https://registry.npmjs.org/remark-lint-ordered-list-marker-style/-/remark-lint-ordered-list-marker-style-3.1.2.tgz",
"integrity": "sha512-62iVE/YQsA0Azaqt8yAJWPplWLS47kDLjXeC2PlRIAzCqbNt9qH3HId8vZ15QTSrp8rHmJwrCMdcqV6AZUi7gQ==",
"dev": true,
"dependencies": {
"@types/mdast": "^3.0.0",
"unified": "^10.0.0",
"unified-lint-rule": "^2.0.0",
"unist-util-generated": "^2.0.0",
"unist-util-position": "^4.0.0",
"unist-util-visit": "^4.0.0"
},
"funding": {
"type": "opencollective",
"url": "https://opencollective.com/unified"
}
},
"node_modules/remark-lint-prohibited-strings": { "node_modules/remark-lint-prohibited-strings": {
"version": "3.1.0", "version": "3.1.0",
"resolved": "https://registry.npmjs.org/remark-lint-prohibited-strings/-/remark-lint-prohibited-strings-3.1.0.tgz", "resolved": "https://registry.npmjs.org/remark-lint-prohibited-strings/-/remark-lint-prohibited-strings-3.1.0.tgz",

View File

@ -10,6 +10,7 @@
"remark-lint-heading-increment": "^3.1.2", "remark-lint-heading-increment": "^3.1.2",
"remark-lint-heading-style": "^3.1.2", "remark-lint-heading-style": "^3.1.2",
"remark-lint-no-shell-dollars": "^3.1.2", "remark-lint-no-shell-dollars": "^3.1.2",
"remark-lint-ordered-list-marker-style": "^3.1.2",
"remark-lint-prohibited-strings": "^3.1.0", "remark-lint-prohibited-strings": "^3.1.0",
"remark-lint-unordered-list-marker-style": "^3.1.2", "remark-lint-unordered-list-marker-style": "^3.1.2",
"remark-stringify": "^10.0.3", "remark-stringify": "^10.0.3",

View File

@ -52,14 +52,14 @@ We are working on adding a lot of features to the core integration. We have reve
### How can I clean a specific room? ### How can I clean a specific room?
We plan to make the process simpler in the future, but for now, it is a multi-step process. We plan to make the process simpler in the future, but for now, it is a multi-step process.
1) Make sure to first name the rooms in the Roborock app; otherwise, they won't appear in the debug log. 1. Make sure to first name the rooms in the Roborock app; otherwise, they won't appear in the debug log.
2) [Enable debug logging](/docs/configuration/troubleshooting/#enabling-debug-logging) for this integration and reload it. 2. [Enable debug logging](/docs/configuration/troubleshooting/#enabling-debug-logging) for this integration and reload it.
3) Search your logs for 'Got home data' and find the attribute rooms. 3. Search your logs for 'Got home data' and find the attribute rooms.
4) Write the rooms down; they have a name and 6 digit ID. 4. Write the rooms down; they have a name and 6 digit ID.
5) Go to {% my developer_call_service service="vacuum.send_command" title="**Developer Tools** > **Services** > **Vacuum: Send Command**" %}. Select your vacuum as the entity and `get_room_mapping` as the command. 5. Go to {% my developer_call_service service="vacuum.send_command" title="**Developer Tools** > **Services** > **Vacuum: Send Command**" %}. Select your vacuum as the entity and `get_room_mapping` as the command.
6) Go back to your logs and look at the response to `get_room_mapping`. This is a list of the 6-digit IDs you saw earlier to 2-digit IDs. In your original list of room names and 6-digit IDs, replace the 6-digit ID with its pairing 2-digit ID. 6. Go back to your logs and look at the response to `get_room_mapping`. This is a list of the 6-digit IDs you saw earlier to 2-digit IDs. In your original list of room names and 6-digit IDs, replace the 6-digit ID with its pairing 2-digit ID.
7) Now, you have the 2-digit ID that your vacuum uses to describe a room. 7. Now, you have the 2-digit ID that your vacuum uses to describe a room.
8) Go back to {% my developer_call_service service="vacuum.send_command" title="**Developer Tools** > **Services** > **Vacuum: Send Command**" %} then type `app_segment_clean` as your command and `segments` with a list of the 2-digit IDs you want to clean. Then, add `repeat` with a number (ranging from 1 to 3) to determine how many times you want to clean these areas. 8. Go back to {% my developer_call_service service="vacuum.send_command" title="**Developer Tools** > **Services** > **Vacuum: Send Command**" %} then type `app_segment_clean` as your command and `segments` with a list of the 2-digit IDs you want to clean. Then, add `repeat` with a number (ranging from 1 to 3) to determine how many times you want to clean these areas.
Example: Example:
```yaml ```yaml