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
{{ message }}
This repository has been archived by the owner on Oct 9, 2023. It is now read-only.
I have an issue with makeValidDataAttribute expecting to always get only defined values.
When I run an application where the hypernova server fails and the hypernova client (hypernova-python in my case) does not include the hypernova-id data attribute the call-chain from load("Component") ends up running from_script with an object like {hypernova-key: "Component", hypernova-id: null}. When that then wants to normalize the attributes it fails on hypernova-id.
By reading the commit that added the functionality of multiple copies of the same component I thought supporting hypernova-id was optional?
Context
Code is transpiled with webpack 2 and babel-loader with presets es2015 and react.
I have an issue with
makeValidDataAttribute
expecting to always get only defined values.When I run an application where the hypernova server fails and the hypernova client (hypernova-python in my case) does not include the hypernova-id data attribute the call-chain from
load("Component")
ends up runningfrom_script
with an object like{hypernova-key: "Component", hypernova-id: null}
. When that then wants to normalize the attributes it fails onhypernova-id
.By reading the commit that added the functionality of multiple copies of the same component I thought supporting
hypernova-id
was optional?Context
Code is transpiled with webpack 2 and babel-loader with presets es2015 and react.
Example html:
Error-code:
The text was updated successfully, but these errors were encountered: