Files
plane/apps
Manish Gupta 999514fffc fix: 404 instead of a hollow 200 when a global view does not exist
Review catch, verified before fixing. WorkspaceViewViewSet.retrieve resolves the
view with .first() and serialized the result unconditionally, so a member asking
for an id that does not exist got 200 with every field null or empty
(`{"name": "", "description": "", "filters": null, ...}`) and a recent-visit
enqueued for a nonexistent entity. Because get_queryset() is scoped to the URL
workspace, the same happened for a real view id belonging to a different
workspace.

Returns 404, matching the other retrieve endpoints.

Noted while confirming this, not fixed here: the project-level sibling
IssueViewViewSet.retrieve has the same .first() pattern and then dereferences
`issue_view.owned_by`, which raises AttributeError on None rather than answering
404 — a 500 instead of a hollow 200. Different method, so it gets its own ticket
rather than widening this one.

Co-authored-by: Plane AI <noreply@plane.so>
2026-08-27 11:04:03 +05:30
..
2026-08-16 23:36:30 +05:30