X Tutup
Skip to content

chore(build): Clean-up TypeScript build#7941

Closed
chuckjaz wants to merge 1 commit intoangular:masterfrom
chuckjaz:cleanTrees
Closed

chore(build): Clean-up TypeScript build#7941
chuckjaz wants to merge 1 commit intoangular:masterfrom
chuckjaz:cleanTrees

Conversation

@chuckjaz
Copy link
Copy Markdown
Contributor

@chuckjaz chuckjaz commented Apr 6, 2016

Chore

  • What is the current behavior? (You can also link to an open issue here)

Broccoli builds refer to files outside the input tree requiring custom file name resolution.

  • What is the new behavior (if this is a feature change)?

Broccoli builds only refer to files in the input tree and no longer require custom file name resolution.

  • Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

No.

  • Other information:

The TypeScript parser now only references files that are in broccoli trees.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

this this right? shouldn't we achieve this by setting rootDir to inputPath instead?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

They are both the same but I can change this to this.compilerOptions.rootDir if that is more clear.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

the rootDir is already set to inputPath. no?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Yes. They are equivalent. I felt it was more clear with this.treeInputPath as it is much more clear that these files are from the broccoli input tree.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I misunderstood what you were saying here. Sorry about that.

TypeScript requires all files to be under rootDir and doesn't resolve relative files returned via getScriptFileNames() to rootDir. It is expected that getScriptFileNames() returns resolved filenames which is what this does. Changing rootDir, at least for 1.7.5, is not sufficient.

@IgorMinar IgorMinar added pr_state: LGTM action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews labels Apr 7, 2016
@IgorMinar
Copy link
Copy Markdown
Contributor

lgtm except for the dart analyzer failure on travis + the seeminly duplicate inputPath prefixing via both rootDir and getScriptFileNames

@IgorMinar
Copy link
Copy Markdown
Contributor

can you please update the commit message to build(broccoli): .... per https://github.com/angular/angular/blob/master/CONTRIBUTING.md#type

The TypeScript parser now only references files that are in broccoli trees.
@chuckjaz
Copy link
Copy Markdown
Contributor Author

chuckjaz commented Apr 7, 2016

The dart failure seems to be a flake, unrelated to my changes.

@chuckjaz chuckjaz added action: merge The PR is ready for merge by the caretaker and removed action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews labels Apr 7, 2016
@IgorMinar
Copy link
Copy Markdown
Contributor

@chuckjaz thanks!

@mary-poppins
Copy link
Copy Markdown

Merging PR #7941 on behalf of @alxhub to branch presubmit-alxhub-pr-7941.

@angular-automatic-lock-bot
Copy link
Copy Markdown

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 8, 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 cla: yes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

X Tutup