We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The MapProps interface doesn't match with the props defined in component level.
MapProps
While doing some thing like
<Map fog={props.fog} />
Where props: MapProps
props: MapProps
Getting error like
This is not just limited to the fog but there couple of other props with same issue.
fog
And doing something like this
<Map {...props} />
where props: MapProps, results in bunch of TS errors.
Looks like the cause for this is how the types are defined: On the component level the fog props is defined as:
On MapProps interface it is defined as:
Prop types should be consistent across the exported MapProps interface and the component
Step to reproduce is explained in detail in the the description section
react-map-gl
mapbox-gl
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description
The
MapProps
interface doesn't match with the props defined in component level.While doing some thing like
Where
props: MapProps
Getting error like
This is not just limited to the
fog
but there couple of other props with same issue.And doing something like this
where
props: MapProps
, results in bunch of TS errors.Looks like the cause for this is how the types are defined:
On the component level the
fog
props is defined as:On
MapProps
interface it is defined as:Expected Behavior
Prop types should be consistent across the exported
MapProps
interface and the componentSteps to Reproduce
Step to reproduce is explained in detail in the the description section
Environment
react-map-gl
: 7.0.21mapbox-gl
: 2.13.0Logs
No response
The text was updated successfully, but these errors were encountered: