-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Expose VPFeatures #4355
Open
4 tasks done
Comments
florian-sattler
pushed a commit
to florian-sattler/vitepress
that referenced
this issue
Nov 12, 2024
florian-sattler
added a commit
to florian-sattler/vitepress
that referenced
this issue
Nov 12, 2024
I've added a possible solution in the form of a pull request. However, I'm happy to iterate on this if desired. |
@brc-dd Do you have any opinions on this? You've been actively involved in the related issue, and your insight would be very appreciated 🙂 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
As a user, I want to use the
VPFeatures
component on any page at any location I want, as it is a very useful as well as highly encapsulated component. However, currently onlyVPHomeFeatures
is exposed, which is only a thin wrapper aroundVPFeatures
that just ensures frontmatter is used for parametrization. This prevents using this otherwise standalone component freely.Describe the solution you'd like
Add
VPFeatures
tovitepress/theme.d.ts
e.g. by modifying eithersrc/client/theme-default/index.ts
orsrc/client/theme-default/without-fonts.ts
.Describe alternatives you've considered
Trying to use only the related classes does not work due to the scoped styles. Other ideas have failed, similar to the issues described in #2595.
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: