Scope-aware operation name disambiguation based on output mode

[sendreams]

Background

Currently, orval ensures global uniqueness of generated operation names across the entire OpenAPI document.
When name collisions are detected, numeric suffixes (1, 2, 3, …) are appended automatically.

While this behavior is safe, it produces unintuitive results when using structured output modes such as:

mode: tags

mode: split

In these modes, operations are already grouped into separate output files, but name disambiguation is still applied globally, even when there is no conflict within the same file.

This leads to cases where operations inside a single tag/file are unnecessarily renamed, for example:

export const {
  update1,
  listCompanyProject1,
  create1,
  delete3
} = ...

even though no duplicates exist within that tag.

[melloware]

Yep but in theory you could have dupes within the same tag in split tags mode etc. so the dupes are calculated up front before split mode etc.

[sendreams]

Yep but in theory you could have dupes within the same tag in split tags mode etc. so the dupes are calculated up front before split mode etc.

True, but duplicates within a single tag are rare and have minimal business impact. In contrast, global duplicates introduce too much uncertainty.

[melloware]

Probably also true. Not sure how easy it would be to rearrange the ordering of operations here.