-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
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
Error: Unsupported map representation "stringpairs" #72
Comments
well, it parses, thankfully! but alas no, I obviously skipped this one as can't-be-bothered in my initial passes: Lines 307 to 314 in fae8a4c
but it would be useful, I know Eric uses this one a lot in the things he does and it's useful for representing all sorts of unixy things. Do you have a direct use for it now? It probably wouldn't be too hard to add, it'd just need some solid testing because of all the possible variations and the fixtures I wrote for stringpairs are pretty .. basic. |
I don't have a direct use for it at the moment, and don't see one any time soon. It just happened to be the first thing I tested from the representations since it looked cool. 😁 |
So, no rush on implenting this if there's higher priority stuff, could just leave this open as a tracking issue. If you have time, it would be useful to document which features are unsupported in the README however. |
I was attempting to use the stringpairs representation for a schema, but got an error when trying to pass it to the
create()
function intyped.js
.Here's the schema I used:
Did I do something wrong? It appears as though
typed.js
just doesn't support this functionality.The text was updated successfully, but these errors were encountered: