-
Notifications
You must be signed in to change notification settings - Fork 59
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
Cannot read property 'split' of undefined (error with new Grid stuff) #176
Comments
So I actually had some incorrect properties defined on a rule meant only for flex box css. I removed the:
And all seems fine now. Still, it never threw an error before and its a little strange that it does now (setting too many css rules incorrectly shouldn't be cause for error). |
Sorry for being that late with the response. Didn't see that issue at all. |
@robinweser I don't think this is the same error as it was made last year. But the error message is the same. more details here: |
@matthetherington Would you be willing to add a PR adding a string check before that |
@robinweser #190 here you go |
We can close this now I think. |
Hi, I'm realizing that this issue is actually not fixed. I was previously passing a default empty string
This doesn't happen with other properties as far as I know. (Fela just ignores them, as expected). |
react-native-web crash with the same error on flex related stuff. one case is when the 'flex' value is a negative value. |
Just updated some of my packages today and noticed this error off the bat:
I have a Fela rule where I pass a lot of things of which some properties are allowed to be undefined - which are then forgotten in the regular behaviour. I use the fela plugin for inline style prefixing. But it seems that for the grid rules, there is no check being run to ignore prefixing on undefined values:
So this property converter is throwing an error:
If you're curious what my rule looks like:
All those parameters passed in are optional. Haven't had an issue until the recent update to
inline-style-prefixer
.I guess this could be seen as an issue in
fela-plugin-inline-style-prefixer
. But I think the prefixer should be smart enough to ignore undefined values (or at least throw a decent error).The text was updated successfully, but these errors were encountered: