Incorrect import statement when both overriden_models and separate_models options are used #756
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.
First of all, I want to say thank you for this great project which I've only been experimenting with for two days and the DevEx it provides is almost flawless. In my case, some field of type
Map<String, List<SomeDto>>
inside a model was created asMap<String, dynamic>
, but thanks to theoverriden_models
option I was able to handle it with a custom model class. I was also using theseparate_models
option and that led to some hard-codedimport 'overriden_models.dart';
lines inside the*.swagger.dart
files, which I think is a bug. This PR replaces the hard-coded import statement with the value ofimportUrl
field fromoptions.overridenModels
.Fixes #745