Skip to content

chore(docs): rename @private to @internal#4477

Closed
alexeagle wants to merge 1 commit intoangular:masterfrom
alexeagle:internal
Closed

chore(docs): rename @private to @internal#4477
alexeagle wants to merge 1 commit intoangular:masterfrom
alexeagle:internal

Conversation

@alexeagle
Copy link
Copy Markdown
Contributor

The latter is understood by TypeScript's --stripInternal option, so this lets us
rely more on the tooling provided by typescript team.

Part of #3082

@alexeagle alexeagle added the action: review The PR is still awaiting reviews from at least one requested reviewer label Oct 2, 2015
@mhevery mhevery added pr_state: LGTM and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Oct 2, 2015
@mhevery mhevery assigned alexeagle and unassigned mhevery Oct 2, 2015
@alexeagle
Copy link
Copy Markdown
Contributor Author

cc @IgorMinar @petebacondarwin I've tried to be careful in the docs generation code to replace the right private references, but I'm not confident how to test that the docs are generated the same way. Should I do more careful testing before merging this?

@petebacondarwin
Copy link
Copy Markdown
Contributor

If you generate the docs in angular.io, both before and after your changes, then you should be able to see if there are any changes via git.

@petebacondarwin
Copy link
Copy Markdown
Contributor

Hold on, we have migrated all these dgeni packages over to angular.io. You should be making changes there.

alexeagle added a commit to alexeagle/angular.io that referenced this pull request Oct 2, 2015
alexeagle added a commit to alexeagle/angular.io that referenced this pull request Oct 2, 2015
alexeagle added a commit to angular/angular.io that referenced this pull request Oct 5, 2015
The latter is understood by TypeScript's --stripInternal option, so this lets us
rely more on the tooling provided by typescript team.
@IgorMinar
Copy link
Copy Markdown
Contributor

as @petebacondarwin said this PR needs to be split into two. one with annotation changes in our code base and then the second one should be for angular.io repo to update the dgeni package.

@IgorMinar
Copy link
Copy Markdown
Contributor

I'll send a PR removing the dgeni code from our angular/angular

@alexeagle
Copy link
Copy Markdown
Contributor Author

the angular.io change is already merged actually (Naomi merged the PR a bit before I was ready...)

@alexeagle alexeagle added the action: merge The PR is ready for merge by the caretaker label Oct 6, 2015
@mary-poppins
Copy link
Copy Markdown

Merging PR #4477 on behalf of @alexeagle to branch presubmit-alexeagle-pr-4477.

@mary-poppins mary-poppins removed the action: merge The PR is ready for merge by the caretaker label Oct 6, 2015
IgorMinar added a commit to IgorMinar/angular that referenced this pull request Oct 6, 2015
This stuff now lives in angular.io repo.

Related to angular#4477
IgorMinar added a commit that referenced this pull request Oct 6, 2015
This stuff now lives in angular.io repo.

Related to #4477

Closes #4552
@alexeagle
Copy link
Copy Markdown
Contributor Author

merged in f7aa890

@alexeagle alexeagle closed this Oct 7, 2015
@alexeagle alexeagle deleted the internal branch October 7, 2015 00:10
@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 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants