Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes incorrect type name and factory method name generation in aliased scenario #5496

Merged
merged 3 commits into from
Sep 30, 2024

Conversation

andrueastman
Copy link
Member

Closes #5404

When trying to find the factory method in the TypeScriptConventionService.cs file, the method was looking for the factory method in the from the namespace. In the event that a namespace is a child of the namespace has a factory method with the same name, this may find the incorrect method(that's why it was aliased).

As the target model will be in the same file as its factory method, the PR narrows the search to work from the file searching from the namespace will be too broad.

Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
66.7% Coverage on New Code (required ≥ 80%)

See analysis details on SonarCloud

@andrueastman andrueastman marked this pull request as ready for review September 30, 2024 12:15
@andrueastman andrueastman requested a review from a team as a code owner September 30, 2024 12:15
@andrueastman
Copy link
Member Author

@andrueastman andrueastman merged commit c3a18ca into main Sep 30, 2024
208 of 209 checks passed
@andrueastman andrueastman deleted the andrueastman/fixTsGeneration branch September 30, 2024 13:57
@andrueastman andrueastman changed the title WIP: Fixes incorrect type name and factory method name generation in aliased scenario Fixes incorrect type name and factory method name generation in aliased scenario Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

[TS] Incorrect type name and factory method name generation in aliased scenario
2 participants