Angular Style Guide

Versions

There are multiple versions of Angular, and thus there are multiple versions of the guide. Choose your guide appropriately.

Angular 1 Style Guide

The Angular 1 Style Guide.

Angular 2 Style Guide

The Angular 2 Style Guide.

Angular Team Endorsed

Special thanks to Igor Minar, lead on the Angular team, for reviewing, contributing feedback, and entrusting me to shepherd this guide.

Purpose

Opinionated Angular style guide for teams by @john_papa

If you are looking for an opinionated style guide for syntax, conventions, and structuring Angular applications, then step right in. These styles are based on my development experience with Angular, presentations, Pluralsight training courses and working in teams.

The purpose of this style guide is to provide guidance on building Angular applications by showing the conventions I use and, more importantly, why I choose them.

If you like this guide, check out my Angular Patterns: Clean Code course at Pluralsight which is a companion to this guide.

Angular Patterns: Clean Code

Community Awesomeness and Credit

Never work in a vacuum. I find that the Angular community is an incredible group who are passionate about sharing experiences. Many of my styles have been from the many pair programming sessions Ward Bell and I have had. My most excellent friend Ward has helped influence the ultimate evolution of these guides.

Contributing

Open an issue first to discuss potential changes/additions. If you have questions with the guide, feel free to leave them as issues in the repository. If you find a typo, create a pull request. The idea is to keep the content up to date and use github’s native feature to help tell the story with issues and PR’s, which are all searchable via google. Why? Because odds are if you have a question, someone else does too! You can learn more here at about how to contribute.

By contributing to this repository you are agreeing to make your content available subject to the license of this repository.

Process

1. Discuss the changes in a GitHub issue.
2. Open a Pull Request, reference the issue, and explain the change and why it adds value.
3. The Pull Request will be evaluated and either merged or declined.

License

tldr; Use this guide. Attributions are appreciated.

Copyright

Copyright (c) 2014-2016 John Papa

(The MIT License)

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Back to top



Angular Style Guide

版本

有多个版本的Angular,因此有多个版本的指南。适当选择您的指南。

角度1风格指南

角度2风格指南

角度2风格指南

角色团队赞同

特别感谢Igor Minar领导Angular团队审查,提供反馈意见,并委托我来指导本指南。

目的

@john_papa

如果您正在为语法,约定和构造Angular应用程序寻找一个有意见的风格指南,那么请直接进入。这些风格基于我的开发经验, Angular < / a>,演示文稿,多媒体培训课程,并在团队中工作。

此样式指南的目的是通过显示我使用的约定,更重要的是为什么选择它们来提供有关构建Angular应用程序的指导。

If you like this guide, check out my Angular Patterns: Clean Code course at Pluralsight which is a companion to this guide.

社区迷信和信用

不要在真空中工作。我发现Angular社区是一个非常热衷于分享经验的不可思议的团队。我的许多风格来自许多对节目编排会议 Ward Bell ,我已经有了。我最好的朋友沃德已经帮助影响了这些指南的最终进化。

贡献

首先打开一个问题来讨论潜在的更改/添加。如果您对本指南有任何疑问,请随时将其作为存储库中的问题。如果您发现输入错误,请创建拉取请求。这个想法是让内容保持最新状态,并使用github的本机功能来帮助讲述有问题的问题和PR,这些都可以通过谷歌搜索。为什么?因为赔率是有问题的,有人也有!您可以在这里了解更多有关如何贡献的信息。

通过贡献于此存储库,您同意根据该存储库的许可,使您的内容可用。

过程

1. Discuss the changes in a GitHub issue.
2. Open a Pull Request, reference the issue, and explain the change and why it adds value.
3. The Pull Request will be evaluated and either merged or declined.

许可证

tldr;使用本指南。归功于欣赏。

版权所有

版权所有(c)2014-2016 约翰·帕帕

许可)

任何人获得许可,免费授予 该软件和相关文档文件的副本( 软件),无限制地处理软件,包括 但不限于使用,复制,修改,合并,发布, 分发,再许可和/或出售本软件的副本,以及 允许提供软件的人员遵守 以下条件:

上述版权声明和本许可声明应为 包含在本软件的所有副本或大部分内容中。

该软件按原样提供,不提供任何形式的保证, 明示或默示,包括但不限于担保 适销性,特定用途适用性和非侵权性。 在任何情况下,作者或版权所有者均不承担任何责任 索赔,损害或其他责任,无论是在合同行为, 侵权行为或以其他方式引起的或与本协议相关的其他信息 软件或软件中的使用或其他交易。

返回页首




相关问题推荐