Skip to content

Fix duplicate operation ids in overloads that are composable. - #645

Merged
Andrew Omondi (andrueastman) merged 2 commits into
support/v1from
andrueastman/fixRegression
Jan 22, 2025
Merged

Fix duplicate operation ids in overloads that are composable.#645
Andrew Omondi (andrueastman) merged 2 commits into
support/v1from
andrueastman/fixRegression

Conversation

@andrueastman

Copy link
Copy Markdown
Contributor

Follow up to #642

Regression introduced due duplicate operation ids. The change doesn't seem like it was replicated in the v2 branch merge at #641. So no need of a second PR.

@sonarqubecloud

Copy link
Copy Markdown

@baywetVincent Biret (baywet) left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fix, can you please also reflect the changes in v2?

@andrueastman
Andrew Omondi (andrueastman) deleted the andrueastman/fixRegression branch January 22, 2025 11:52
@andrueastman

Copy link
Copy Markdown
ContributorAuthor

Just to confirm here Vincent Biret (@baywet), the v2 PR didn't end up with the same regression if you compare the diff of the two PRs,
#642 and #641.

Furthermore, the assertions on the head of the main(v2) branch looks correct/consistent with what we expect.

Assert.Equal("Customers.Customer.MyFunction1.MyFunction2-c53d",operation1.OperationId);

@baywet

Copy link
Copy Markdown
Member

Thank you for double checking!

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@andrueastman@baywet