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
ngcc - some SourceMap URLs are incorrect #29556
Conversation
…er and Renderer We have already removed this concept from the public API. This just cleans it out altogether. The `targetPath` was an alternative output path to the original `basePath`. This is not really a very useful concept, since the actual target path of each output file is more complex and not consistently relative to the `basePath`.
Previously we were using absolute paths, but since at rendering time we do not know exactly where the file will be written it is more correct to change to using relative paths. This is actually better all round since it allows the folders to be portable to different machines, etc.
Previously we were writing `.d.ts` and `.d.ts.map` to different folders.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not directly related to this PR, but the docs for Renderer#renderFile() out outdated (and mention targetPath
).
Previously we were using absolute paths, but since at rendering time we do not know exactly where the file will be written it is more correct to change to using relative paths. This is actually better all round since it allows the folders to be portable to different machines, etc. PR Close #29556
Previously we were writing `.d.ts` and `.d.ts.map` to different folders. PR Close #29556
…er and Renderer (angular#29556) We have already removed this concept from the public API. This just cleans it out altogether. The `targetPath` was an alternative output path to the original `basePath`. This is not really a very useful concept, since the actual target path of each output file is more complex and not consistently relative to the `basePath`. PR Close angular#29556
…ar#29556) Previously we were using absolute paths, but since at rendering time we do not know exactly where the file will be written it is more correct to change to using relative paths. This is actually better all round since it allows the folders to be portable to different machines, etc. PR Close angular#29556
…ar#29556) Previously we were writing `.d.ts` and `.d.ts.map` to different folders. PR Close angular#29556
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. |
// FW-1197