feat: include subproject tasks (rebase of #2272) - #2939
Conversation
Preview DeploymentPreview deployments for this PR are available at:
The preview environment will start automatically on first visit. Subsequent pushes to this PR will update the Run locally with Dockerdocker pull ghcr.io/go-vikunja/vikunja:pr-2939
docker run -p 3456:3456 ghcr.io/go-vikunja/vikunja:pr-2939Last updated for commit 5edc7b5 |
|
auggie review |
|
Please take a look at the failing ci. |
|
Thanks for taking the effort to rebase this! Does that mean you're also taking over the PR? |
Hey @kolaente and @JamesBatten, the UI and syntax fixes are done, so the CI should pass. The database changes are going to stretch my abilities, but I'll dive into moving the variable to the Task Collection this weekend to give it a try. |
|
Unfortunatly, CI is failing again. Happy to assist on the DB changes. |
1187749 to
90ced65
Compare
|
I tried building this PR myself two days ago, and after removing the duplicate line the project was built correctly, but the buttons ,,Include subprojects" were turning off milliseconds after interacting with them. I have no knowledge of this codebase, so I tried stitching together whatever seemed to match, but there seemed to be many inconsistencies, namely in files:
Given all other toggleable filters append a ?query=value to the URL and this one didn't, I assumed this was supposed to be handled client-side rather than persisted to the DB, so I moved the whole thing over to work that way instead (as is shown above), but that didn't work either and it just stopped doing anything whatsoever, but buttons did persist (didn't turn off) I have no idea what the "correct" intended design is here (persisted view setting vs. client-side query param), and honestly at this point looking at the PR, I'm not sure the PR itself has settled on one either. |
|
Small follow-up: moved the duplicated |
|
damnm, i was looking for this feature. did we ensure that members of parent project can see tasks of child projects and its own, while child project members can only see their own |
Yes this is the case. I added a test to check it as well. |
Pins vikunja to a self-built image of PR go-vikunja/vikunja#2939, which shows tasks from child projects in parent project views. Built from zshzebra/vikunja@finish-subprojects (v2.3.0-816-g13b0f4f4e) via a workflow in that fork, and pinned by digest because the deploy role runs `pull: always`. Upstream's preview image was not usable: it was built seven weeks stale and persisted the setting as a project_views column, whereas the current branch nests it in the existing filter JSON. Migrating onto the preview build would have written view settings into a column the merged version never reads. The healthcheck moves to vikunja's own healthcheck subcommand; the image is distroless so the previous wget check could never have worked.
… ReadAll complexity
|
Hi - just bumping this in case anyone has time to finalise it - it looks like the only required test failure is "file is not properly formatted" which hopefully should be an easy fix, in fact it looks like it is just a surplus blank line. Sadly I don't have the practical development skills to add a commit, run the tests etc. or I would do so. |
…walk Upstream changed Project.ParentProjectID to *int64, so using it directly as a map key no longer compiles. parentID() treats nil as 0, matching how the rest of the codebase dereferences it.
4c7e119 to
423a851
Compare
This PR revives @JamesBatten's work from #2272 so it is ready for merge. My changes are rebasing against main, resolving conflicts, and fixing linter errors. Supersedes and closes #2272 .