Skip to content

Commit 9a8db0e

Browse files
Sherwin-14wchcpsievert
authored
Attempted to fix the broken link on custom components page (#207)
* Removed @output decorator * Remove trailing whitespace * Fixed the broken link in the custom components page --------- Co-authored-by: Winston Chang <[email protected]> Co-authored-by: Carson Sievert <[email protected]>
1 parent ef51158 commit 9a8db0e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/custom-components-pkg.qmd

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ filters:
55
---
66

77

8-
While there are a large number of pre-built [components available for Shiny,](components/) there are times when you may want to create your own. In this article we’ll walk through the process of creating a custom input component package for Shiny. We’ll be using React and Typescript to build the component, but the process is similar for other languages and frameworks.
8+
While there are a large number of pre-built [components available for Shiny,](https://shiny.posit.co/py/components/) there are times when you may want to create your own. In this article we’ll walk through the process of creating a custom input component package for Shiny. We’ll be using React and Typescript to build the component, but the process is similar for other languages and frameworks.
99

1010
::: {.callout-note}
1111
If you just want to build a one-off component for a single app, a full package may be overkill. See the accompanying article [Custom JavaScript component](custom-component-one-off.html) for a simpler approach.

0 commit comments

Comments
 (0)