diff --git a/.remarkrc.cjs b/.remarkrc.cjs index 09668d1fc6a4..b5b908449b25 100644 --- a/.remarkrc.cjs +++ b/.remarkrc.cjs @@ -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', '\\.,;:'], ], } diff --git a/package.json b/package.json index a5088ca6da25..27591a3c67bc 100644 --- a/package.json +++ b/package.json @@ -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" }, diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml index b9be16ad0ef3..5bec991da53c 100644 --- a/pnpm-lock.yaml +++ b/pnpm-lock.yaml @@ -34,6 +34,9 @@ importers: remark-lint-heading-increment: specifier: ^3.1.1 version: 3.1.1 + remark-lint-no-heading-punctuation: + specifier: ^3.1.1 + version: 3.1.1 remark-lint-restrict-elements: specifier: workspace:* version: link:packages/remark-lint-restrict-elements @@ -7905,6 +7908,17 @@ packages: unist-util-visit: 4.1.2 dev: true + /remark-lint-no-heading-punctuation@3.1.1: + resolution: {integrity: sha512-ZexHx4rmsjKVF1/Fvdig0yOgpWl0wFa43+sqg880HT3PW9KmEczjSRkwlMaTlVgDzC0paNn2FXfQMuEQW4YDLg==} + dependencies: + '@types/mdast': 3.0.11 + mdast-util-to-string: 3.2.0 + unified: 10.1.2 + unified-lint-rule: 2.1.1 + unist-util-generated: 2.0.1 + unist-util-visit: 4.1.2 + dev: true + /remark-math@5.1.1: resolution: {integrity: sha512-cE5T2R/xLVtfFI4cCePtiRn+e6jKMtFDR3P8V3qpv8wpKjwvHoBA4eJzvX+nVrnlNy0911bdGmuspCSwetfYHw==} dependencies: diff --git a/website/pages/en/developing/developer-faqs.mdx b/website/pages/en/developing/developer-faqs.mdx index 3abac24f447f..726464abe60b 100644 --- a/website/pages/en/developing/developer-faqs.mdx +++ b/website/pages/en/developing/developer-faqs.mdx @@ -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)