-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
compilerOptions.rootDirs - folder list order should define the copying order. #30497
Comments
Debates about which behavior constitutes "correct" aside, this would be an extremely confusing and disruptive breaking change to roll out after the fact. |
@RyanCavanaugh |
@RyanCavanaugh |
We can start with a suggestion if you like. Just to set expectations, I don't think we'd be inclined to complicate file resolution even further unless it was very often-requested. |
Hi, The name of the option (or if there is an additional option at all) does not matter. We just need something like java's compiletime classpath (with possibilty to impose resolve order to make generated files obscure the sources). Of course, we could copy the files accordingly before build, but doing this manually we could drive IDE like vscode into confusion (the IDE should follow the settings of actual build). For this reason the "standard" classpath behavior would be appreciated. To make sure I understood You properly, Should I create a new feature request? |
A new issue clearly outlining the suggestion would be the next step, yes |
@RyanCavanaugh |
Folder list order in
rootDirs
should define the copying order (e.g. which file overwrites which, in case the same filename exists in more than one ofrootDirs
folder).now, no matter the order in which
rootDirs
folders are provided, the import "prefers" the file in the same folder.Why its important? Consider we have some decorator based generator which enhances the source classes (like java's lombok). In this case we need to impose higher precedence on generated classes.
The text was updated successfully, but these errors were encountered: