Skip to content
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

Closed
wants to merge 3 commits into from

Conversation

petebacondarwin
Copy link
Member

// FW-1197

…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.
@petebacondarwin petebacondarwin added area: core Issues related to the framework runtime comp: ivy labels Mar 27, 2019
@petebacondarwin petebacondarwin requested a review from a team as a code owner March 27, 2019 22:14
@ngbot ngbot bot added this to the needsTriage milestone Mar 27, 2019
Copy link
Contributor

@alan-agius4 alan-agius4 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@petebacondarwin petebacondarwin added target: major This PR is targeted for the next major release action: merge The PR is ready for merge by the caretaker labels Mar 28, 2019
Copy link
Member

@gkalpak gkalpak left a 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).

packages/compiler-cli/ngcc/src/rendering/renderer.ts Outdated Show resolved Hide resolved
@jasonaden jasonaden closed this in c456b73 Mar 28, 2019
jasonaden pushed a commit that referenced this pull request Mar 28, 2019
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
jasonaden pushed a commit that referenced this pull request Mar 28, 2019
Previously we were writing `.d.ts` and `.d.ts.map` to different
folders.

PR Close #29556
@petebacondarwin petebacondarwin deleted the FW-1197 branch April 2, 2019 09:00
wKoza pushed a commit to wKoza/angular that referenced this pull request Apr 17, 2019
…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
wKoza pushed a commit to wKoza/angular that referenced this pull request Apr 17, 2019
…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
wKoza pushed a commit to wKoza/angular that referenced this pull request Apr 17, 2019
…ar#29556)

Previously we were writing `.d.ts` and `.d.ts.map` to different
folders.

PR Close angular#29556
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker area: core Issues related to the framework runtime cla: yes target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants