Add 'Is empty (NULL)' and 'Is not empty (NOT NULL)' to field Filter Operators Options

@tetranz thanks for the patch. Tested the patch on 8.9. It's working on my end.

Please find the SS attached for ref.

Also, tested the patch on 9.1, it works as intended.

Thanks for the patch. It works perfectly for me. Hopefully, this gets committed soon. It's always a bit annoying & unexpected if you need patches for very basic stuff like that.

I have applied the patch #2 and it works fine after applying the patch. The option for Is empty (NULL) and Is not empty (NOT NULL) will be there in the options list after applying the patch.

Thanks for working on this, but this can't be committed without automated tests. So we need to add some.

Setting this to be a feature request.

I created a custom field of type boolean and this patch didn't work in that case.

tested the patch (#2) on 8.9.15 and i confirm it's working

for entity reference Base field ...

@tetranz I have applied Patch
Patch is working fine for reference sharing screenshot ....

let's try with latest 10.1 to "gain attention"

Rebased the PR and updated with tests for checking "allow empty" option for not required fields.

Will need a 11.x branch as that's the latest development branch.
Recommend starting a new one.

Also think the issue summary could use some love. Recommend adding the default template.

Updates:
- Create new MR for 11.x branch
- Update issue summary

so i think we're back to Needs Review.

Confirmed the MR addresses the Null and Not Null options are available for the filename.

May need a change record but will see if the committer agrees.

Doing RTBC issue triage.

I read the IS and used the steps to reproduce and successfully confirmed the problem. Since this is a change to the user interface there should be screenshots linked to in the Issue Summary. I read the comments and do not see any comment saying that the code and test were reviewed. I also wonder if the test fails without the fix.

Regarding a change record, yes add one. This is for views which is an interface with many, many options so we should let everyone know about it. The CR should have screen shots.

Setting back to NW.

Adding link to Documentation Gate about when to add change records, https://www.drupal.org/about/core/policies/core-change-policies/core-gat...

Updates:
- screenshots for issue summary
- patch with tests only for seeing ... it fails.
- Added change record draft: https://www.drupal.org/node/3370509

Failed asserting that an array has the key 'allow empty'.
And the patch with tests without "fix" fails ... as intended

So it think we're back to RTBC

"Remove" the patch with tests without "fix" ... so it wouldn't change the issue status ... no more

@vasike, thank you for doing that last bit of work.

There are comments that this patch works, although not for boolean but that makes sense to me. What I still do not see is that anyone has reviewed the code. I scanned it but I don't know enough of views to do a proper review. I have added that to the IS in the remaining tasks.

I updated credit but, as always, it needed to be checked by the committer.

Change seems small and addresses the issue.

Am curious why this just appears on file views outside the core one.

Adding a patch version of the MR for composer patching. After reviewing the solution, we will use the patch on our sites to support this functionality for base fields.

Overlaps with #3322402: Add 'Is empty (NULL)' and 'Is not empty (NOT NULL)' operators to boolean field filtering

Nice work on this! I posted a couple small nitpick suggestions on the MR.

I also think this should maybe have some UI test coverage, in addition to the kernel test coverage that's being added already?

Can someone test if #3322402: Add 'Is empty (NULL)' and 'Is not empty (NOT NULL)' operators to boolean field filtering solves the issue here? If not what should be addressed here that isn't addressed other there.

@smustgrave it's not the same ... it should be clear from issue summary - User interface changes section
So this is about missing those options ... the other issue it's about their actually filtering ...

Anyway updated the MR with latest 11.x and also checked the tests ... they fail without the fix.

So I think this should be back on track.

I've tested https://git.drupalcode.org/project/drupal/-/merge_requests/4060 and it worked very well!

Cleaned up the ticket some hiding old patches and closing an old MR.

Rebased the 11.x branch as it was 200 commits back.

Did run the test-only feature and got

1) Drupal\Tests\views\Kernel\Entity\EntityViewsDataTest::testBaseTableFields
Failed asserting that an array has the key 'allow empty'.
/builds/issue/drupal-3098560/core/modules/views/tests/src/Kernel/Entity/EntityViewsDataTest.php:433
FAILURES!
Tests: 9, Assertions: 323, Failures: 1.
Exiting with EXIT_CODE=1

Which shows test coverage.

Still green. Again just did a rebase not submit new code so think I’m good to mark

Not eligible for backport as it's a feature request.

Committed a551f2b and pushed to 11.x. Thanks!

Also published the change record.

Amending attribution.