Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit f067ef2

Browse files
author
Ivan Carballo
committedDec 8, 2015
Merge pull request ribot#16 from ribot/fix_section_numbering
Fix 1.2 section numbering
2 parents 1ff6230 + 00fe34d commit f067ef2

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed
 

‎project_and_code_guidelines.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11,11 +11,11 @@ Class names are written in [UpperCamelCase](http://en.wikipedia.org/wiki/CamelCa
1111

1212
For classes that extend an Android component, the name of the class should end with the name of the component; for example: `SignInActivity`, `SignInFragment`, `ImageUploaderService`, `ChangePasswordDialog`.
1313

14-
### 1.2.1 Resources files
14+
### 1.2.2 Resources files
1515

1616
Resources file names are written in __lowercase_underscore__.
1717

18-
#### 1.2.1.1 Drawable files
18+
#### 1.2.2.1 Drawable files
1919

2020
Naming conventions for drawables:
2121

@@ -53,7 +53,7 @@ Naming conventions for selector states:
5353
| Selected | `_selected` | `btn_order_selected.9.png` |
5454

5555

56-
#### 1.2.1.2 Layout files
56+
#### 1.2.2.2 Layout files
5757

5858
Layout files should match the name of the Android components that they are intended for but moving the top level component name to the beginning. For example, if we are creating a layout for the `SignInActivity`, the name of the layout file should be `activity_sign_in.xml`.
5959

@@ -69,13 +69,13 @@ A slightly different case is when we are creating a layout that is going to be i
6969

7070
Note that there are cases where these rules will not be possible to apply. For example, when creating layout files that are intended to be part of other layouts. In this case you should use the prefix `partial_`.
7171

72-
#### 1.2.1.3 Menu files
72+
#### 1.2.2.3 Menu files
7373

7474
Similar to layout files, menu files should match the name of the component. For example, if we are defining a menu file that is going to be used in the `UserActivity`, then the name of the file should be `activity_user.xml`
7575

7676
A good practice is to not include the word `menu` as part of the name because these files are already located in the `menu` directory.
7777

78-
#### 1.2.1.4 Values files
78+
#### 1.2.2.4 Values files
7979

8080
Resource files in the values folder should be __plural__, e.g. `strings.xml`, `styles.xml`, `colors.xml`, `dimens.xml`, `attrs.xml`
8181

0 commit comments

Comments
 (0)
Please sign in to comment.