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
This is because we use raw column headers from the csv input as dom element ids and css classes.
It of course isn't helped by our conversion of numerical values to interval memberships with headers like age_[23.45552, 32.948889) which break CSS pretty hard. Spaces are also problematic for similar reasons
We'll need to find a way to sanitize strings to be safe for use as CSS classes and dom ids. UrlEncode would probably work, but feels a little too clumsy. Maybe someone out there has already solved this problem? I'll do some digging.
I don't completely understand but for the short term, please just be
specific about what's allowed and not allowed in csv file. If you state it
here, I can update the docs.
This is because we use raw column headers from the csv input as dom
element ids and css classes.
It of course isn't helped by our conversion of numerical values to
interval memberships with headers like age_[23.45552, 32.948889) which
break CSS pretty hard. Spaces are also problematic for similar reasons
We'll need to find a way to sanitize strings to be safe for use as CSS
classes and dom ids. UrlEncode would probably work, but feels a little too
clumsy. Maybe someone out there has already solved this problem? I'll do
some digging.
—
Reply to this email directly or view it on GitHub #13 (comment)
.
This issue may be obviated by the discussion in #12. If we rewrite the interface to avoid exposing/requiring binarized columns, much of this will become simpler.
The real resolution of this will require discussion with a js developer.
Error: Syntax error, unrecognized expression: .target#yrs since phd_(-3.037, 4.4]
The text was updated successfully, but these errors were encountered: