⚓ refactor(loadConfigModels): Stricter Default Model Fallback #2239
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Refactored the
loadConfigModels
function to return default models based on the endpoint, rather than the fetch basis. This change ensures that the correct default models are loaded for each endpoint.loadConfigModels
to return default models on an endpoint basis, instead of a fetch basis.loadConfigModels.spec
to include stricter tests for default model matching, ensuring the new implementation adheres to the expected behavior.TEndpoint
type/typedef for better code readability and maintainability.Change Type
Testing
Ensure that all tests, including the updated
loadConfigModels.spec
tests, pass successfully.Checklist