-
-
Notifications
You must be signed in to change notification settings - Fork 122
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
Unable to validate FeatureCollection #82
Comments
That looks to be a bug. This is the problematic line. This should probably return an error. |
Thanks for the bug report! 🐛 |
@frewsxcv No problem, glad to help! Does this mean however that all validations are in effect not working as an empty string is returned every time? Also, would it be a better idea to use a boolean instead of a string for 'valid' ? |
From what I can tell, we return an empty string if the validation is successful or if we've encountered an unknown type. I'm not a huge fan of the current format personally, so if you think you know a better format for this, let me know. It might make sense to have a new class
Yes, a boolean for that value would definitely be an improvement. |
While we're at it, maybe Another pattern (inspired from Marshmallow) would be to have a |
I have created a pull request that fixes this bug. |
Hello,
I was trying to see whether the is_valid would work for feature collection. I tested using the Example GeoJSON Feature Collection.
However it seems that it returns valid for just about anything
Is there a different way to go about this or is FeatureCollection validation not supported at this moment?
The text was updated successfully, but these errors were encountered: