Update default props

[AnnMarieW]

closes #2919

I updated all the components listed in #2919 except for dcc.Location because it's still a class component.

• validate if it works with the typescript components
• I have added tests, or extended existing tests, to cover any new features or bugs fixed in this PR

optionals

• I have added entry in the CHANGELOG.md
• If this PR needs a follow-up in dash docs, community thread, I have mentioned the relevant URLS as follows
  • this GitHub #PR number updates the dash docs
  • here is the show and tell thread in Plotly Dash community

[AnnMarieW]

Another dependency to update - our version of eslint does not seem to support the spread operator. eslint/eslint#10307

> eslint src scripts

/home/circleci/dash/components/dash-html-components/src/components/A.react.js
  12:52  error  Parsing error: Unexpected token ..

For example, this error is from defining the defaults like this in A.react.js

const A = ({n_clicks = 0, n_clicks_timestamp = -1, ...props}) => {

There is an error for each component.

[gvwilson]

@AnnMarieW can you please let us know if you're still working on this one or is it ready for review? thanks - @gvwilson

[AnnMarieW]

Hi @gvwilson

I'm afraid, I've hit a roadblock on this one. Here's the current status:

• The components listed in issue 2919 are updated so that the defaults are defined in the function signature. I verified that the default props are set correctly in the component and the docstrings are generated correctly to show the defaults.
• The sample typescript component is updated. I verified that the defaults are set correctly in the component, however the docstrings do not show the default values.

I found this project that parses the default props from the function signature in typescript components, however, I'm stuck trying to integrate that logic into extract-meta.js

If someone could help with that piece, I could probably finish the rest (ie tests) However, I'm traveling for a few weeks, and would be happy to turn this project over to someone if you'd like to get it wrapped up sooner.

[gvwilson]

@T4rk1n please have a look at this one and help @AnnMarieW move it forward when you can. thanks - @gvwilson

[gvwilson]

some questions but no blockers

[gvwilson]

this seems kind of important :-)

[AnnMarieW]

I changed this to get tests to pass, but @T4rk1n can you confirm if this is OK?

[T4rk1n]

Yes that is the good type.

[gvwilson]

apologies, but can you please explain what the impact of this one will be?

[T4rk1n]

It's a linting that conflicted with the default notation on param functions.

[gvwilson]

do we have colors and other constants scattered elsewhere through the code as well or is there a way to consolidate them all in one place? (very low priority, not worth holding up this PR for)

[gvwilson]

again, can we (in future?) replace magic color constants with names that are all defined in one place?