Skip to content

Universal: Integrate CLI wiki material and copy edit#25752

Closed
jbogarthyde wants to merge 1 commit intoangular:masterfrom
jbogarthyde:jb-cli-universal
Closed

Universal: Integrate CLI wiki material and copy edit#25752
jbogarthyde wants to merge 1 commit intoangular:masterfrom
jbogarthyde:jb-cli-universal

Conversation

@jbogarthyde
Copy link
Copy Markdown
Contributor

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[x] Documentation content changes
[ ] angular.io application / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Added more succinct CLI-oriented info at beginning as a summary, made the existing ToH example more specifically tutorial-style.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

@jbogarthyde jbogarthyde added comp: docs area: server Issues related to server-side rendering target: patch This PR is targeted for the next patch release labels Aug 30, 2018
@mary-poppins
Copy link
Copy Markdown

@CaerusKaru
Copy link
Copy Markdown
Member

Not sure if this PR is the appropriate place for this, but we recently removed the Webpack part of the Universal build process in universal and universal-starter. cc @vikerman @Toxicable @IgorMinar for guidance.

@jbogarthyde
Copy link
Copy Markdown
Contributor Author

This is exactly the right place to correct the current doc :-)
Can you mark up the exact parts of the doc that should be removed or changed?
And also, the content should get a complete technical review from everyone involved, if possible.

@mary-poppins
Copy link
Copy Markdown

@mary-poppins
Copy link
Copy Markdown

@jenniferfell jenniferfell added the action: review The PR is still awaiting reviews from at least one requested reviewer label Sep 4, 2018
@mary-poppins
Copy link
Copy Markdown

@mary-poppins
Copy link
Copy Markdown

@mary-poppins
Copy link
Copy Markdown

@mary-poppins
Copy link
Copy Markdown

@mary-poppins
Copy link
Copy Markdown

@jbogarthyde jbogarthyde removed the request for review from vikerman September 18, 2018 17:50
@mary-poppins
Copy link
Copy Markdown

@mary-poppins
Copy link
Copy Markdown

@mary-poppins
Copy link
Copy Markdown

@vikerman
Copy link
Copy Markdown
Contributor

We don't need to include the webpack CLI info as it's not needed.

Copy link
Copy Markdown
Contributor

@jenniferfell jenniferfell left a comment

Choose a reason for hiding this comment

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

I only looked at the overall structure in the right nav. LGTM except the two things we talked about in slack.

Comment thread aio/content/guide/universal.md Outdated
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.

From our slack...to avoid duplicate heading, maybe "Modify your app and configuration"

Comment thread aio/content/guide/universal.md Outdated
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.

In the preview that I looked at, this heading isn't rendering correctly

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.

Fixed it already, and the md is now correct. Still not rendering though - don't know what else to do to fix it.

@jenniferfell
Copy link
Copy Markdown
Contributor

@vikerman Just to confirm, these changes also apply to v6, yes?

@mary-poppins
Copy link
Copy Markdown

@vikerman
Copy link
Copy Markdown
Contributor

@jenniferfell - Yes. Applies to V6 as well.

@vikerman
Copy link
Copy Markdown
Contributor

Approved. Restarting the flaky tests

@vikerman vikerman added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Oct 12, 2018
@ngbot
Copy link
Copy Markdown

ngbot Bot commented Oct 12, 2018

I see that you just added the PR action: merge label, but the following checks are still failing:
    failure status "ci/circleci: integration_test" is failing
    failure status "continuous-integration/travis-ci/pr" is failing

If you want your PR to be merged, it has to pass all the CI checks.

If you can't get the PR to a green state due to flakes or broken master, please try rebasing to master and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

@vikerman
Copy link
Copy Markdown
Contributor

@jbogarthyde - Can you please rebase the PR? Tests continue to fail (clearly unrelated to this PR but would be better to get it passing cleanly before merge)

@jbogarthyde jbogarthyde force-pushed the jb-cli-universal branch 2 times, most recently from 90f12c8 to 6b1c429 Compare October 12, 2018 21:40
@jbogarthyde
Copy link
Copy Markdown
Contributor Author

Rebased and squashed

@mary-poppins
Copy link
Copy Markdown

@mary-poppins
Copy link
Copy Markdown

@mary-poppins
Copy link
Copy Markdown

@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 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: server Issues related to server-side rendering cla: yes target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants