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

Don't silently discard requests to set QgsFieldExpressionWidget to an empty expression #6312

Merged
merged 1 commit into from Feb 12, 2018

Conversation

nyalldawson
Copy link
Collaborator

This causes issues in lots of places - e.g. a field constraint is always set to the first field in a layer, and cannot be removed.

I've looked at all calls to setField and without exception they should accept that setting the field to an empty string results in an empty expression.

Fixes #14325, and supersedes #2810

to an empty expression

This causes issues in lots of places - e.g. a field constraint
is always set to the first field in a layer, and cannot be
removed.

I've looked at all calls to setField and without exception
they should accept that setting the field to an empty string
results in an empty expression.

Fixes qgis#14325
@nyalldawson
Copy link
Collaborator Author

@3nids here you go - something else to puzzle your head over.

Copy link
Member

@3nids 3nids left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems fine to me as far as I understand it!

@nyalldawson nyalldawson merged commit efdaf5f into qgis:master Feb 12, 2018
@nyalldawson nyalldawson deleted the field_exp_null branch February 28, 2018 04:12
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.

None yet

2 participants