fix(core): Fixed condition for using barrel
import in split-tags
mode
#1122
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.
Status
READY
Description
Due to the changes in this PR,
barrel
is no longer used forimport
ofschema
files when the following conditions are met:tags-split
is specified formode
schemas
It looks like you are expecting
barrel
to not be used forimport
ofschema
ifindexFiles
isfalse
.But, as a result,
barrel
is no longer used forimport
ofschema
files even if the value ofindexFiles
istrue
. Incidentally, by default the value ofindexFiles
istrue
.I made a small change because if
indexFiles
istrue
, I want to usebarrel
forimport
as before.Todos
Steps to Test or Reproduce
when
indexFiles
isfalse
,barrel
is not used forimport
ofschema
false
forindexFiles
inorval.config.js
as shown below:orval
executionbarrel
is not used ingen/endpoints/pets/pets.ts
when
indexFiles
istrue
,barrel
is used forimport
ofschema
true
forindexFiles
inorval.config.js
as shown below:orval
executionbarrel
is used ingen/endpoints/pets/pets.ts