Skip to content

enable remark-lint-no-heading-punctuation rule #355

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 1 commit into from
Apr 26, 2023
Merged

enable remark-lint-no-heading-punctuation rule #355

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
1 change: 1 addition & 0 deletions .remarkrc.cjs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,5 +4,6 @@ module.exports = {
['remark-lint-first-heading-level', 2],
['remark-lint-restrict-elements', { type: 'heading', depth: 1 }],
'remark-lint-heading-increment',
['remark-lint-no-heading-punctuation', '\\.,;:'],
],
}
1 change: 1 addition & 0 deletions package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,7 @@
"remark-frontmatter": "^4.0.1",
"remark-lint-first-heading-level": "^3.1.1",
"remark-lint-heading-increment": "^3.1.1",
"remark-lint-no-heading-punctuation": "^3.1.1",
"remark-lint-restrict-elements": "workspace:*",
"typescript": "5.0.4"
},
Expand Down
14 changes: 14 additions & 0 deletions pnpm-lock.yaml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion website/pages/en/developing/developer-faqs.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,7 @@ Not currently, as mappings are written in AssemblyScript. One possible alternati

Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created: Start blocks

## 18. Are there some tips to increase the performance of indexing? My subgraph is taking a very long time to sync.
## 18. Are there some tips to increase the performance of indexing? My subgraph is taking a very long time to sync

Yes, you should take a look at the optional start block feature to start indexing from the block that the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)

Expand Down