I'm not sure I understand why the parameter is named differently at all parts of the stack. The frontend is namedoutdated -- which makes the most sense to me for the name. But the backend name isupdated and then the database parameter isupdate_active. Why not have them consistent?

There is only two names from a code POV.

I am usingUsingActive on the database because that is physically the database column we are checking. It felt odd to put "updated" there because that word doesn't feel semantically correct.

For the api I used the wordupdated since that is the phrasing of the original ticket. And we use the language "Update" on the workspaces page when a workspace is out-of-date. So the FE tends to useupdated as the language.

"Outdated" is just the helper text for the quick search query list. I felt this would be more commonly used that searching for all updated workspaces. And the ticket was requesting this as the feature. So that is the one I made as the quick link.

If you click it though, the language is "updated".

Personally I thinkoutdated makes more sense as the query param but ultimately up to you.

I will useoutdated as the query param 👍