diff options
| author | Craig Jennings <c@cjennings.net> | 2026-06-06 15:17:51 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-06-06 15:17:51 -0500 |
| commit | 184b94538cdcc807aa382f2766beb0b615776e43 (patch) | |
| tree | 3ec7bb5bad619f13ae01951cf59e62216c972a0d /tests | |
| parent | 23c741c4dc8a3e5a753b3c42389b8c673052d2ce (diff) | |
| download | pearl-184b94538cdcc807aa382f2766beb0b615776e43.tar.gz pearl-184b94538cdcc807aa382f2766beb0b615776e43.zip | |
feat(views): route grouping consumers through the effective-grouping resolver
Phase 4 of the interactive-grouping spec: the integration that makes an interactive grouping survive a refresh. The full render (pearl--build-org-content) and both merge-refresh paths (the dirty-merge branch and pearl--merge-query-result) read the source's grouping straight from :group. I pointed all three at pearl--effective-grouping instead, so a buffer the user grouped by hand redraws the same way rather than snapping back to the view's server grouping.
The swap is backward-compatible: with no :client-group set, the resolver returns :group, so a server-grouped view renders exactly as before. 2 render tests lock both directions: a :client-group overrides the server :group, and a server-only view still groups by :group.
Diffstat (limited to 'tests')
| -rw-r--r-- | tests/test-pearl-grouping.el | 27 |
1 files changed, 27 insertions, 0 deletions
diff --git a/tests/test-pearl-grouping.el b/tests/test-pearl-grouping.el index 13a84d5..a30bcc1 100644 --- a/tests/test-pearl-grouping.el +++ b/tests/test-pearl-grouping.el @@ -327,5 +327,32 @@ SE-1 has a comment subtree; SE-2 has no assignee.") 'no-issues))) (should-not (plist-get (pearl--read-active-source) :client-group)))) +;;; render integration — consumers read pearl--effective-grouping (phase 4) + +(defconst test-pearl-grouping--issues + (list (list :id "i1" :identifier "SE-1" :title "Alpha" + :state '(:name "In Progress") :project '(:name "Apollo") :priority 2) + (list :id "i2" :identifier "SE-2" :title "Beta" + :state '(:name "Todo") :project '(:name "Apollo") :priority 1)) + "Two normalized issues with distinct states, one shared project.") + +(ert-deftest test-pearl-build-org-content-client-group-overrides-server () + "The full render groups by :client-group, overriding a view's server :group." + (let ((out (pearl--build-org-content + test-pearl-grouping--issues + '(:type view :name "V" :id "vid" :group "project" + :client-group "workflowState")))) + (should (string-match-p "^\\*\\* In Progress$" out)) + (should (string-match-p "^\\*\\* Todo$" out)) + (should-not (string-match-p "^\\*\\* Apollo$" out)))) + +(ert-deftest test-pearl-build-org-content-server-group-when-no-client () + "With no :client-group, the full render still honors the view's server :group." + (let ((out (pearl--build-org-content + test-pearl-grouping--issues + '(:type view :name "V" :id "vid" :group "project")))) + (should (string-match-p "^\\*\\* Apollo$" out)) + (should-not (string-match-p "^\\*\\* In Progress$" out)))) + (provide 'test-pearl-grouping) ;;; test-pearl-grouping.el ends here |
