feat(tsc-wrapped): Support of vinyl like config file was added#13987
feat(tsc-wrapped): Support of vinyl like config file was added#13987alxhub merged 7 commits intoangular:masterfrom
Conversation
There was a problem hiding this comment.
instead of any, can it be string|{path:string}, or can you introduce an interface that structurally matches like VinylFile?
There was a problem hiding this comment.
again, can you avoid any?
There was a problem hiding this comment.
I don't think we should repeat all the assertions here - you just need to assert enough to be sure the vinyl file path and contents were used. Just check that some of your config was used
There was a problem hiding this comment.
this import is now shadowed by the variable on line 25, can you avoid that?
There was a problem hiding this comment.
can you add isVinylFile to ./vinyl that returns project is VinylFile
See User-Defined Type Guards on https://www.typescriptlang.org/docs/handbook/advanced-types.html
Then just call isVinylFile instead of casting here
There was a problem hiding this comment.
Aha, type guard - nice. Sure will add.
There was a problem hiding this comment.
use !isVinylFile to narrow the type instead of casting
There was a problem hiding this comment.
you shouldn't need a cast here anymore - the project type will have the VinylFile narrowed out since isVinylFile is known to be false in this else clause
There was a problem hiding this comment.
Wow, very tricky, but now I know it :)
|
I'm getting conflicts when rebasing this on |
This feature was implemented in order to provide easier way of use in gulp
Test case config was fixed.
Code was corrected according to the remarks
Code formatting was corrected
Type guard was introduced for VinylFile
5d47856 to
0f1a713
Compare
|
@alxhub, Rebasing and resolving conflicts are done. |
…ar#13987) This feature was implemented in order to provide easier way of use in gulp
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This feature was implemented in order to provide easier way of use in gulp
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behavior? (You can also link to an open issue here)
What is the new behavior?
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: