Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead

[jeadys]

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[x] Other... Please describe:

defaultProps currently deprecated and will be removed in React 18.3.0

Current behavior

// Example from LineChart.tsx

import React, { FC } from 'react';
import { AreaChart, AreaChartProps } from '../AreaChart';
import { LineSeries } from './LineSeries';

export type LineChartProps = AreaChartProps;

export const LineChart: FC<Partial<LineChartProps>> = (props) => (
  <AreaChart {...props} />
);

LineChart.defaultProps = {
  ...AreaChart.defaultProps,
  series: <LineSeries />
};

Expected behavior

// Example from LineChart.tsx

import React, { FC } from 'react';
import { AreaChart, AreaChartProps } from '../AreaChart';
import { LineSeries } from './LineSeries';

export type LineChartProps = AreaChartProps;

export const LineChart: FC<Partial<LineChartProps>> = ({
  series = <LineSeries />,
  ...props
}) => <AreaChart {...props} />;

What is the motivation / use case for changing the behavior?

defaultProps currently deprecated and will be removed in React 18.3.0

Environment

Libs:
- react version: 18.2.0
- reaviz version: 14.14.4

[amcdnl]

Unfortuantly the way the APIs are used it needs to be initialized via default props. We are going to need to re-evaluate our strategy for this in the upcoming release. Thanks for highlighting, if you are interested in contributing let me know.

[jeadys]

yea, would like to contribute where needed.