improve endpoint naming

[metaforx]

For automatic schema generation, it would help to have distinctive naming per endpoint. It would help developers to know which endpoint they are actually addressing and what response to expect.

Problem
When generating clients from API endpoints using OpenAPI schema, it is really cumbersome to detect the difference between the various menu/submenu/breadcrumbs endpoints to choose from, just by number.

const { data } = cmsMenuRetrieve({
  composable: 'useFetch',
  path: {
    language: defaultLanguage,
  },
const { data } = cmsMenuRetrieve2({
  composable: 'useFetch',
  path: {
    language: defaultLanguage,
    extra_active: 999,
    extra_inactive: 999,
    from_level: 1,
    to_level: 3,
  },

Solution

• Add custom name per endpoint

Confirmation

• Fetch schema and generate clients
• Use an API testing tool like Bruno

[fsbraun]

@metaforx Can you suggest better names - I believe the repeated names come from using the "same" endpoint with varying number of parameters (with the parameters not provided to fall back to default values).

[metaforx]

@metaforx Can you suggest better names - I believe the repeated names come from using the "same" endpoint with varying number of parameters (with the parameters not provided to fall back to default values).

I agree. I try to come up with something meaningful :)