Remove calculateRequestOrder Function and fix bug

[DevMrRober]

Summary

This PR removes the calculateRequestOrder function. The previous function was deemed unnecessary due to its redundant logic and lack of unique functionality.

Changes made

• Removed function calculateRequestOrder

• Removed call to calculateRequestOrder function, which calculated the order of requests based on operationGroupingOrder and requestsSize.

• Updated request creation logic:

  • Changed request creation logic to use requests.size() as the key in requests.putIfAbsent(), ensuring that each new request is added with a unique identifier based on the current size of the request map.

Reason for change

• The original implementation included unnecessary complexity that generated a bug that only generated 2 operations if they were on the same path.

Tests

• All existing tests have been run to ensure that no functionality has been affected by this change.
• Requests are added correctly without being removed, and existing functionality remains intact.

Related issue

• Fixes issue [BUG] Only generate 2 operations swagger to k6 #19110

Reviewers

• Please review the changes and provide feedback on the removal of the feature.

[wing328]

Thanks for the PR but your commit (as shown in the Commits tab) is not linked to your Github account, which means this PR won't count as your contribution in https://github.com/OpenAPITools/openapi-generator/graphs/contributors.

Let me know if you need help fixing it.

Ref: https://github.com/OpenAPITools/openapi-generator/wiki/FAQ#how-can-i-update-commits-that-are-not-linked-to-my-github-account

[wing328]

cc @mostafa

[DevMrRober]

Sorry, I made a mistake the first time, it should be right now.

[mostafa]

LGTM! Thanks for your contribution.

[DevMrRober]

@wing328 when will this PR be applied?

[wing328]

just merged. thanks for the PR

samples updated via 25b8341