Unassigned filter based on detecting the string null

[smutniak]

Fixes #2119

[Copilot]

Pull request overview

Fixes the “Assigned To = Unassigned” filter returning no results by treating the literal string "null" (as received from the client/filter serialization) the same as an actual null filter value when building the dynamic submission list SQL.

Changes:

• Update assignee.email filter SQL generation to interpret "null" as an “unassigned” sentinel and generate IS NULL predicates accordingly.

Comments suppressed due to low confidence (1)

src/main/java/org/tdl/vireo/model/repo/impl/SubmissionRepoImpl.java:807

• This change introduces support for the literal string "null" as the Unassigned filter value, but there is no regression test covering it. Please add a backend test (integration or repo-level) that creates assigned + unassigned submissions and asserts the "assignee.email" filter with filterValue "null" returns only the unassigned submissions.

                    for (String filterString : submissionListColumn.getFilters()) {
                        sqlBuilder = new StringBuilder();

                        if (filterString == null) {
                            sqlBuilder.append("a.email IS NULL");
                        } else if (filterString.equalsIgnoreCase("null")) {
                            sqlBuilder.append("a.email IS NULL");
                        } else if (submissionListColumn.getExactMatch()) {
                            sqlBuilder.append("a.email = '").append(filterString).append("'");
                        } else {
                            sqlBuilder.append("LOWER(a.email) LIKE '%").append(escapeString(filterString)).append("%'");
                        }

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[smutniak]

This requires a bigger change than just this location. Also this value comes from the database rather than 'user input'.