Skip to content

Commit

Permalink
[docs] Fix interior section links in Base docs that feature hooks (#3…
Browse files Browse the repository at this point in the history
…3948)

fix anatomy links
  • Loading branch information
samuelsycamore committed Aug 17, 2022
1 parent a7dbc3c commit 8d6bae2
Show file tree
Hide file tree
Showing 7 changed files with 7 additions and 7 deletions.
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

0 comments on commit 8d6bae2

Please sign in to comment.