feat: sort labels by name,asc in shopping lists

[seamuslowry]

What type of PR is this?

• feature

What this PR does / why we need it:

This is an initial (partial) implementation of the request in this discussion: #3297.

In controller_labels.py it extends the PaginationQuery class to override the default values for order_by and order_direction so that call to this endpoint will use those as the default, rather than using nothing.

Update frontend/pages/shopping-lists/_id.vue to pass orderBy: "name" and orderDirection: "asc" on label refreshes

Which issue(s) this PR fixes:

No issues reference this specifically. This is intended as an initial step towards the feature requested in This is an initial implementation of the request in this discussion: #3297.

Special notes for your reviewer:

I am not experienced with FastAPI or Mealie conventions. I am happy to apply the same pattern to the paginated GET requests of the other listed models, but I wanted to get some input on the pattern and implementation before copying the pattern around.

Testing

• in Swagger UI, I tested passing other values for order_by and order_direction to verify they were used over the new defaults. Similarly, tested with other pre-existing values like per_page to ensure they were still respected.
• in the UI, I validated that the request to get labels when adding a new item to a shopping list (which wasn't specifying order_by and order_direction is now specifying name and asc

[michael-genson]

I don't think this is something we want to do on the backend; is there somewhere in particular on the frontend you labels aren't sorted alphabetically? If so, we should address it there

[seamuslowry]

I've only noted seeing it when trying to add an item to a shopping list

I thought it would make sense to change the defaults for the endpoint, get it for free everywhere that doesn't specify. But I'm happy to make it in that one spot on the frontend instead

[michael-genson]

Ah okay, that makes sense. Is it possible to use the label store here instead of using userApi? The store defaults to name ascending, and it would save us an API call (we're already using the label store in that same file). Something like:

const { store: allLabels, actions: labelActions } = useLabelStore();  // this already partially exists on line 605

And then we can just call actions.refresh() and get rid of refreshLabels (and allLabels will automatically be updated).

[seamuslowry]

Updated. But I used labelActions.getAll rather than labelActions.refresh

The refresh call seems to call the api directly without specifying any defaults: https://github.com/mealie-recipes/mealie/blob/mealie-next/frontend/composables/partials/use-actions-factory.ts#L106. So it does not resolve the issue.

[michael-genson]

Thanks for keeping with this one!