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] Fix interior section links in Base docs that feature hooks #33948

Merged
merged 1 commit into from Aug 17, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/data/base/components/badge/badge.md
Expand Up @@ -105,7 +105,7 @@ Hooks _do not_ support [slot props](#slot-props), but they do support [customiza
Hooks give you the most room for customization, but require more work to implement.
With hooks, you can take full control over how your component is rendered, and define all the custom props and CSS classes you need.

You may not need to use hooks unless you find that you're limited by the customization options of their component counterparts—for instance, if your component requires significantly different [structure](#component-slots).
You may not need to use hooks unless you find that you're limited by the customization options of their component counterparts—for instance, if your component requires significantly different [structure](#anatomy).
:::

## Customization
Expand Down
2 changes: 1 addition & 1 deletion docs/data/base/components/button/button.md
Expand Up @@ -109,7 +109,7 @@ Hooks _do not_ support [slot props](#slot-props), but they do support [customiza
Hooks give you the most room for customization, but require more work to implement.
With hooks, you can take full control over how your component is rendered, and define all the custom props and CSS classes you need.

You may not need to use hooks unless you find that you're limited by the customization options of their component counterparts—for instance, if your component requires significantly different [structure](#component-slots).
You may not need to use hooks unless you find that you're limited by the customization options of their component counterparts—for instance, if your component requires significantly different [structure](#anatomy).
:::

The `useButton` hook requires the `ref` of the element it's used on.
Expand Down
2 changes: 1 addition & 1 deletion docs/data/base/components/form-control/form-control.md
Expand Up @@ -68,7 +68,7 @@ Hooks _do not_ support [slot props](#slot-props), but they do support [customiza
Hooks give you the most room for customization, but require more work to implement.
With hooks, you can take full control over how your component is rendered, and define all the custom props and CSS classes you need.

You may not need to use hooks unless you find that you're limited by the customization options of their component counterparts—for instance, if your component requires significantly different [structure](#component-slots).
You may not need to use hooks unless you find that you're limited by the customization options of their component counterparts—for instance, if your component requires significantly different [structure](#anatomy).
:::

The demo below shows how to integrate this hook with its component counterpart:
Expand Down
2 changes: 1 addition & 1 deletion docs/data/base/components/input/input.md
Expand Up @@ -103,7 +103,7 @@ Hooks _do not_ support [slot props](#slot-props), but they do support [customiza
Hooks give you the most room for customization, but require more work to implement.
With hooks, you can take full control over how your component is rendered, and define all the custom props and CSS classes you need.

You may not need to use hooks unless you find that you're limited by the customization options of their component counterparts—for instance, if your component requires significantly different [structure](#component-slots).
You may not need to use hooks unless you find that you're limited by the customization options of their component counterparts—for instance, if your component requires significantly different [structure](#anatomy).
:::

The demo below shows how to use the `useInput` hook to create a custom input component that receives all the necessary props:
Expand Down
2 changes: 1 addition & 1 deletion docs/data/base/components/menu/menu.md
Expand Up @@ -125,7 +125,7 @@ Hooks _do not_ support [slot props](#slot-props), but they do support [customiza
Hooks give you the most room for customization, but require more work to implement.
With hooks, you can take full control over how your component is rendered, and define all the custom props and CSS classes you need.

You may not need to use hooks unless you find that you're limited by the customization options of their component counterparts—for instance, if your component requires significantly different [structure](#component-slots).
You may not need to use hooks unless you find that you're limited by the customization options of their component counterparts—for instance, if your component requires significantly different [structure](#anatomy).
:::

The following demo shows how to build a menu using hooks:
Expand Down
2 changes: 1 addition & 1 deletion docs/data/base/components/select/select.md
Expand Up @@ -146,7 +146,7 @@ Hooks _do not_ support [slot props](#slot-props), but they do support [customiza
Hooks give you the most room for customization, but require more work to implement.
With hooks, you can take full control over how your component is rendered, and define all the custom props and CSS classes you need.

You may not need to use hooks unless you find that you're limited by the customization options of their component counterparts—for instance, if your component requires significantly different [structure](#component-slots).
You may not need to use hooks unless you find that you're limited by the customization options of their component counterparts—for instance, if your component requires significantly different [structure](#anatomy).
:::

The following example shows a select that opens when hovered over or focused.
Expand Down
2 changes: 1 addition & 1 deletion docs/data/base/components/slider/slider.md
Expand Up @@ -142,7 +142,7 @@ Hooks _do not_ support [slot props](#slot-props), but they do support [customiza
Hooks give you the most room for customization, but require more work to implement.
With hooks, you can take full control over how your component is rendered, and define all the custom props and CSS classes you need.

You may not need to use hooks unless you find that you're limited by the customization options of their component counterparts—for instance, if your component requires significantly different [structure](#component-slots).
You may not need to use hooks unless you find that you're limited by the customization options of their component counterparts—for instance, if your component requires significantly different [structure](#anatomy).
:::

## Customization
Expand Down