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

Tracking: Documentation #2711

Closed
28 of 38 tasks
Brocco opened this issue Oct 14, 2016 · 19 comments
Closed
28 of 38 tasks

Tracking: Documentation #2711

Brocco opened this issue Oct 14, 2016 · 19 comments
Assignees
Labels
area: docs Related to the documentation P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful

Comments

@Brocco
Copy link
Contributor

Brocco commented Oct 14, 2016

Document the following areas of the CLI:

  • overview
  • new
  • init
  • generate
    • component
    • class
    • directive
    • enum
    • interface
    • module
    • pipe
    • service
  • test
  • build
  • e2e
  • get/set
  • docs
  • eject
  • lint
  • serve
  • angular-cli.json

Tasks:

  • Move readme documentation to the wiki (docs)

Stories for more details:

Nice to have:

Additional:

  • Internationalization usage/story;
    • extraction
    • build
    • serve
    • deploy
@Puigcerber
Copy link
Contributor

Hey guys!

I thought about this yesterday when I discovered that all the generate commands have many options. Any idea of where to start? README.md or a separate guide?

Cheers.

@filipesilva filipesilva added P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful area: docs Related to the documentation labels Oct 15, 2016
@Brocco
Copy link
Contributor Author

Brocco commented Oct 15, 2016

Still trying to figure that out for now, wanted to have a placeholder issue to track against.

@elvirdolic
Copy link

It would be great to put more docs to https://cli.angular.io/ with similiar doc style which is used on angular.io

@hansl
Copy link
Contributor

hansl commented Dec 2, 2016

Next action item:

  • Move the WIKI content to /docs/wiki in the repo. The release should publish the wiki from git.

@Meet91
Copy link

Meet91 commented Dec 6, 2016

Following this updated doc to integrate Bootstrap with angular-cli results into following module conflicts:

jquery.js
tether.js
Details errors are as below:

**ERROR in multi scripts
Module not found: Error: Can't resolve 'C:\word\angular-demo\node_modules\jquery\dist\jquery.js' in 'C:\word\angular-demo\node_modules\angular-cli\models'
@ multi scripts

ERROR in multi scripts
Module not found: Error: Can't resolve 'C:\word\angular-demo\node_modules\tether\dist\js\tether.js' in 'C:\word\angular-demo\node_modules\angular-cli\models'
@ multi scripts**

I'm using below configuration:
angular-cli: 1.0.0-beta.20-4
node: 7.1.0(npm-4.0.3)
os: win32 x64
bootstrap : 3.3.7

Any help in this matter would be really appreciated!

Thanks,
Mitesh

@Brocco
Copy link
Contributor Author

Brocco commented Dec 7, 2016

@Meet91 I just verified my local app with no issues. Based upon your errors it seems like you're attempting to pull in more than just the bootstrap CSS as my guide suggests. If that's not the case please create a separate issue on this repo or post a question on StackOverflow. Make sure to either tag me in the issue and/or link to it here so I can find it. (I don't have a windows environment setup, so I'm testing on macOS v10.12.1)

@nweldev
Copy link
Contributor

nweldev commented Dec 7, 2016

@Meet91 see #3202 (comment), there is a workaround for that

Edit : see #3202 (comment) ... the problem seems to be resolved in beta.22-1

@Meet91
Copy link

Meet91 commented Dec 7, 2016

@noelmace I updated the angular-cli to beta.22-1 and error goes away and also tested with the bootstrap integration and all works great...Thank you so much for responding on such a short period!!!

Brocco added a commit to Brocco/angular-cli that referenced this issue Dec 14, 2016
jeremymwells added a commit to jeremymwells/angular-cli that referenced this issue Jan 7, 2017
jeremymwells added a commit to jeremymwells/angular-cli that referenced this issue Jan 7, 2017
jeremymwells added a commit to jeremymwells/angular-cli that referenced this issue Jan 7, 2017
jeremymwells added a commit to jeremymwells/angular-cli that referenced this issue Jan 7, 2017
@jeremymwells
Copy link
Contributor

@Brocco - can you elaborate a little bit on what you had in mind for Setup of global styles?

@Brocco
Copy link
Contributor Author

Brocco commented Jan 8, 2017

@jeremymwells global styles are the style files referenced via angular-cli.json this would be an overview of:

  1. how to setup a reference here
  2. an overview of the implications of setting up a style here versus within an individual component

This is not meant to be a complicated explanation, just an overview on how to achieve application-wide styling.

jeremymwells added a commit to jeremymwells/angular-cli that referenced this issue Jan 8, 2017
Brocco added a commit to Brocco/angular-cli that referenced this issue Jan 18, 2017
This fix is part of the documentation improvement angular#2711
Brocco added a commit that referenced this issue Jan 18, 2017
This fix is part of the documentation improvement #2711
jeremymwells added a commit to jeremymwells/angular-cli that referenced this issue Jan 18, 2017
jeremymwells added a commit to jeremymwells/angular-cli that referenced this issue Jan 18, 2017
jeremymwells added a commit to jeremymwells/angular-cli that referenced this issue Jan 20, 2017
filipesilva pushed a commit that referenced this issue Jan 24, 2017
filipesilva pushed a commit to filipesilva/angular-cli that referenced this issue Jan 24, 2017
@filipesilva
Copy link
Contributor

@Brocco added angular-cli.json to the list.

MRHarrison pushed a commit to MRHarrison/angular-cli that referenced this issue Feb 9, 2017
MRHarrison pushed a commit to MRHarrison/angular-cli that referenced this issue Feb 9, 2017
MRHarrison pushed a commit to MRHarrison/angular-cli that referenced this issue Feb 9, 2017
@moniuch
Copy link

moniuch commented Feb 27, 2017

I would appreciate if angular-cli docs were constantly updated with minimum requirements of relevant dependencies, for each release.

@hansl hansl self-assigned this Mar 16, 2017
@hansl
Copy link
Contributor

hansl commented Mar 16, 2017

I need to work on a serializer of the documentation for hte JSON Schema.

@hansl hansl added this to the 1.0 Final NON-Blocking milestone Mar 16, 2017
@hansl
Copy link
Contributor

hansl commented Mar 24, 2017

Considering this done. Expect more stories post 1.0.

@moniuch that's a great idea, but we're pretty lax on our requirements. The only relevant dependency is Angular and TypeScript :)

@hansl hansl closed this as completed Mar 24, 2017
@itsnotvalid
Copy link

There is a mismatch to protrator.conf.json that the project line is not e2e but e2e/tsconfig.e2e.json from the generator output.

beforeLaunch: function() {
    require('ts-node').register({
      project: 'e2e/tsconfig.e2e.json'
    });
  },

@mtpultz
Copy link

mtpultz commented Jul 18, 2017

Is there any reference to Setup of global styles that can be subscribed to on GitHub?

@mtpultz
Copy link

mtpultz commented Jul 18, 2017

Found this in the docs https://github.com/angular/angular-cli/blob/master/docs/documentation/stories/global-styles.md, but I think what I meant by global styles was a way to add global Sass variables for use with components during compile. Otherwise, you're always importing a variables file, palette file, etc throughout your Sass files.

@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 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: docs Related to the documentation P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful
Projects
None yet
Development

No branches or pull requests