Skip to content

Conversation

@mkilpatrick
Copy link
Collaborator

While the component registry was a neat idea, no one used it in practice. We're also limiting hybrid functionality at this point.

@github-actions
Copy link
Contributor

Warning: Component files have been updated but no migrations have been added. See https://github.com/yext/visual-editor/blob/main/packages/visual-editor/src/components/migrations/README.md for more information.

"docs:preview": "vitepress preview .",
"generate-registry": "tsx src/components/registry/build-registry.cts",
"build-registry-docs": "pnpm run docs:build && pnpm run generate-registry",
"i18n:insert": "pnpm exec tsx scripts/insertI18n.ts",
Copy link
Contributor

Choose a reason for hiding this comment

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

I think you can also get rid of packages/visual-editor/artifacts.json, packages/visual-editor/config.yaml, packages/starter/components.json and the scripts.components entry in packages/starter/package.json

Copy link
Contributor

Choose a reason for hiding this comment

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

Oh wait I guess artifacts and config.yaml power the documentation site too

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.

3 participants