Skip to content
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.

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

docs: move docs to packageDocumentation #2180

Merged
merged 1 commit into from
Oct 31, 2023

Conversation

achingbrain
Copy link
Member

Since ageir 41.1.0 the contents of the @packageDocumentation tag in the /src/index.ts file of a given module will be copied to the README for that repo under the About section, so move all hand-written README data into @pacakgeDocumentation tags so we can keep the docs up to date in just one place.

Since ageir 41.1.0 the contents of the `@packageDocumentation` tag
in the `/src/index.ts` file of a given module will be copied to the
README for that repo under the `About` section, so move all
hand-written README data into `@pacakgeDocumentation` tags so we
can keep the docs up to date in just one place.
@achingbrain achingbrain requested a review from a team as a code owner October 30, 2023 17:28
@achingbrain achingbrain merged commit 6958136 into master Oct 31, 2023
22 checks passed
@achingbrain achingbrain deleted the docs/move-docs-to-package-documentation branch October 31, 2023 06:58
## Usage

```Typescript
```ts
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You've chosen to keep the Typescript example here (in the README) but moved it to the @packageDocumentation in other instances, is this intentional?

import { createLibp2pNode } from 'libp2p'
import { kadDHT } from '@libp2p/kad-dht'

const node = await createLibp2pNode({
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where was this moved to?

Copy link
Member

@maschad maschad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My main aversion to this is that we lose the ability to lint the TS examples as the typescript-docs-verifier runs on the markdown, I suppose this could be run when the docs are being generated from the packageDocumentation though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants