Skip to content

Conversation

benmccann
Copy link
Member

@benmccann benmccann commented Jul 11, 2024

See sveltejs/svelte#12410. I didn't rename the files here yet to avoid breaking the currently deployed site. We can do that after retiring kit.svelte.dev

Copy link

changeset-bot bot commented Jul 11, 2024

⚠️ No Changeset found

Latest commit: 4951652

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@PuruVJ
Copy link
Contributor

PuruVJ commented Jul 11, 2024

Quick question: It is automatically generated, so why are we adding redundant config?

@benmccann
Copy link
Member Author

More of the description is in the Svelte PR, but the idea is that we want to publish docs for things like the below and we would either need to rename those files and directories to include numbers or use a config or support both. It's probably easier just to support one method and folks seemed to prefer the config route.

https://github.com/sveltejs/vite-plugin-svelte/tree/main/docs
https://github.com/sveltejs/eslint-plugin-svelte/tree/main/docs

@benmccann benmccann closed this Jul 12, 2024
@benmccann benmccann deleted the docs-config branch July 12, 2024 21:26
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