Automatic typescript checking of code in documentation

[AlexanderZeilmann]

Describe the bug

I already brought this up a while ago, that an (semi)-automated checking of the typescript code in the documentation is feasible.

Before working on this, I just wanted to ask how you would prefer a pull request? One big PR with everything? One PR per component? One PR per problem type? Easiest for me is probably one per component.

There are various kinds of errors that can be found. The most common ones are type error and import issues:

Type errors like:

• tab.disabled does not exist on the entries of the tabs array.
  

  primereact/components/doc/accordion/dynamicdoc.js

  Lines 7 to 25 in 54acecd

  	const [tabs] = useState([
  	{
  	header: 'Title I',
  	children: <p className="m-0">Content 1</p>
  	},
  	{
  	header: 'Title II',
  	children: <p className="m-0">Content 2 </p>
  	},
  	{
  	header: 'Title III',
  	children: <p className="m-0">Content 3 </p>
  	}
  	]);
  	const createDynamicTabs = () => {
  	return tabs.map((tab, i) => {
  	return (
  	<AccordionTab key={tab.header} header={tab.header} disabled={tab.disabled}>

• loading refers to a value, but is being used as a type here

  primereact/components/doc/treetable/lazyloaddoc.js

  Line 216 in 54acecd

  const [loading, setLoading] = useState<loading>(true);

• wrong type declarations like the one I fixed here: Add 'help' as severity in splitbutton.d.ts #7446

Import issues like:

• Ripple is imported but not used, Toast is used but not imported

  primereact/components/doc/captcha/captchadoc.js

  Line 41 in 54acecd

  import { Ripple } from 'primereact/ripple';

• importing from the wrong file

  primereact/components/doc/accordion/templatedoc.js

  Lines 64 to 65 in 54acecd

  	import { Avatar } from 'primereact/accordion';
  	import { Badge } from 'primereact/accordion';

In the long run it might make sense to store the code examples in the docs as separate files (that can be type checked & linted more easily) instead of storing the code in strings.

Reproducer

No response

System Information

not applicable

Steps to reproduce the behavior

No response

Expected behavior

No response

[melloware]

One per component would probably be easiest to code review?