You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the MapPanelProvider or MapPanelContent from the latest version of @amsterdam/arm-core (1.0.0) and React and ReactDOM 17.x you get a type error when using either of these components. The type error:
Type '{ children: Element; variant: "panel"; initialPosition: SnapPoint.Halfway; }' is not assignable to type 'IntrinsicAttributes & Props'.
Property 'children' does not exist on type 'IntrinsicAttributes & Props'.typescript(2322)
This error started to appear recently, so may be related to minor or patch updates in another package. No major upgrades have been done. I was able to reproduce this error in CodeSandbox with only React 17 and ARM 1.0:
As (dummy) Touringcar Messages only exist on Acceptance and Production,
and they cannot be accessed locally due to CORS, this PR needs to be
merged with `azure` to get the code on Acceptance.
You might notice the `ts-ignore` comments everywhere. They are added due
to an upstream type error. See [this bug report of
mine](Amsterdam/amsterdam-react-maps#2184) for
more details.
---------
Co-authored-by: Kris de Groot <[email protected]>
Co-authored-by: jjbeekman <[email protected]>
Co-authored-by: Jeroen Beekman <[email protected]>
Co-authored-by: jjbeekman <[email protected]>
Co-authored-by: dependabot-vakgroep-so[bot] <144998647+dependabot-vakgroep-so[bot]@users.noreply.github.com>
Co-authored-by: github-merge-queue <[email protected]>
Co-authored-by: thomasbrockmeier-ams <[email protected]>
Co-authored-by: jjbeekman <[email protected]>
Describe the bug
When using the MapPanelProvider or MapPanelContent from the latest version of
@amsterdam/arm-core
(1.0.0) and React and ReactDOM 17.x you get a type error when using either of these components. The type error:This error started to appear recently, so may be related to minor or patch updates in another package. No major upgrades have been done. I was able to reproduce this error in CodeSandbox with only React 17 and ARM 1.0:
See the type error reproduced in a CodeSandbox
Expected behavior
Property
children
should exist on these element's types. The elements should allow a React child element.The text was updated successfully, but these errors were encountered: