Skip to content
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

[Geometry checker] Make polyLineSize survive empty geometries #2905

Merged
merged 1 commit into from
Mar 14, 2016
Merged

[Geometry checker] Make polyLineSize survive empty geometries #2905

merged 1 commit into from
Mar 14, 2016

Conversation

manisandro
Copy link
Member

Fixes another geometry checker issue reported in bug #13535

@m-kuhn
Copy link
Member

m-kuhn commented Mar 14, 2016

looks good to me.

you've got push rights, no?

@nyalldawson
Copy link
Collaborator

@m-kuhn is being too lenient... I'd like to see a unit test with this! I'm determined to make the geometry classes absolutely rock solid so having tests for all these rare corner cases would be fantastic.

@m-kuhn
Copy link
Member

m-kuhn commented Mar 14, 2016

@nyalldawson I had the same thought but then I noticed it's in a plugin and forgot about it.

@nyalldawson
Copy link
Collaborator

Oh yeah.... @manisandro ignore me, I mistakenly thought this was in the core class, sorry!

@manisandro
Copy link
Member Author

@m-kuhn Yes, got push rights, but a Qt5 test was failing over the weekend. Seems fixed now.

manisandro added a commit that referenced this pull request Mar 14, 2016
[Geometry checker] Make polyLineSize survive empty geometries
@manisandro manisandro merged commit 13d407e into qgis:master Mar 14, 2016
@m-kuhn
Copy link
Member

m-kuhn commented Mar 14, 2016

That was unrelated to your code, the qt5 test still behaves flaky sometimes. I'm trying to figure out the reasons.

@manisandro manisandro deleted the checker_crash branch April 26, 2016 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants