Skip to content

Fixes Issue 996 #997

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

Merged
merged 2 commits into from
Jun 19, 2023
Merged

Fixes Issue 996 #997

merged 2 commits into from
Jun 19, 2023

Conversation

commonsensesoftware
Copy link
Collaborator

Fix for Issue 996

  • You've read the Contributor Guide and Code of Conduct.
  • You've included unit or integration tests for your change, where applicable.
  • You've included inline docs for your change, where applicable.
  • There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.

Summary of the changes (Less than 80 chars)

Description

  • Fixes the scenario where there are multiple EDMs per API version, but they have different models
  • Fixes a scenario that would otherwise prevent the use of a model in different EDMs for the same API version by using the name defined by the EDM, which otherwise defaults to the CLR type name

Fixes #996

@commonsensesoftware commonsensesoftware merged commit 5dc4385 into main Jun 19, 2023
@commonsensesoftware commonsensesoftware deleted the dev/css/issue-996 branch June 19, 2023 19:27
Sign up for free to 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.

Configuring multiple routes each with their own Edm model throws an error
1 participant