-
Notifications
You must be signed in to change notification settings - Fork 12k
docs(@angular/cli): Adds developer documentation and Intellij setup. #16152
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you split this into several commits? Probably three:
- The README updates
- git ignore improvements
- IntelliJ setup
The last may need some discussion with the team as I believe there were previous concerns with adding IDE specific configuration into the repositories.
…ellij configurations. This also changes the local build script to allow negated .gitignore expressions to support these changes.
This should enable using Intellij IDEA/WebStorm to create the project, run it, and start a debugger. I did my best to make sure my personal configuration didn't leak in, someone else will have to confirm that this works reasonably for them too.
9f982fd
to
46de409
Compare
I split up the commits and moved my README edits to |
I wrote down my understanding of the best ways to build/run/test/debug this repository. A couple other random things included here: * Removed an extraneous `debugger;` statement which I kept hitting. * Removed the `watch` scripts which are no longer used and don't need to be supported. * Removed `yarn test-cli-e2e`, as it alters the $PATH and can use the wrong `ng` instance.
Do you think we need to discuss the IntelliJ configs with the team or should I just merge this? |
To be safe, added the discussion label for tomorrow's triage meeting. |
Concerns in the meeting were able not forcing personal configuration settings (such as themeing) directly in the repo. IntelliJ doesn't really put personal settings like that in these files. The settings will be picked up by default, but users should be able to change and modify them as they wish independently from the setting stored in source control. |
Intellij and Webstorm unfortunately don't the use the exact same configuration system.For example, Intellij treats every project as `JAVA_MODULE` but Webstorm doesn't recognize the `JAVA_MODULE`. Therefore, I think that the modules.xml and iml should be left out from version control. refs angular#16152
Intellij and Webstorm unfortunately don't the use the exact same configuration system. For example, Intellij treats every project as `JAVA_MODULE` but Webstorm doesn't recognize the `JAVA_MODULE`. Therefore, I think that the modules.xml and iml should be left out from version control. refs angular#16152
Intellij and Webstorm unfortunately don't the use the exact same configuration system. For example, Intellij treats every project as `JAVA_MODULE` but Webstorm doesn't recognize the `JAVA_MODULE`. Therefore, I think that the modules.xml and iml should be left out from version control. refs angular#16152
Intellij and Webstorm unfortunately don't the use the exact same configuration system. For example, Intellij treats every project as `JAVA_MODULE` but Webstorm doesn't recognize the `JAVA_MODULE`. Therefore, I think that the modules.xml and iml should be left out from version control. refs angular#16152
Intellij and Webstorm unfortunately don't the use the exact same configuration system. For example, Intellij treats every project as `JAVA_MODULE` but Webstorm doesn't recognize the `JAVA_MODULE`. Let's use `WEB_MODULE` as it's recognized by both IDEs. refs angular#16152
Intellij and Webstorm unfortunately don't the use the exact same configuration system. For example, Intellij treats every project as `JAVA_MODULE` but Webstorm doesn't recognize the `JAVA_MODULE`. Let's use `WEB_MODULE` as it's recognized by both IDEs. refs #16152
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
I wrote down my understanding of the best ways to build/run/test/debug this repository. I also included some configs for Intellij to work a little bit better "out of the box".
I tried to get VSCode to work as well, however the debugger there was having trouble loading source maps, so I'll need to come back to that later.
Changes include:
nodemon
as a dev dependency, which is needed for watch executions but wasn't listed.debugger;
statement which I kept hitting.