Git Commit Convention์ด๋?
Git Commit Convention์ ํ๋ก์ ํธ์์ ์ผ๊ด๋ Git ์ปค๋ฐ ๋ฉ์์ง๋ฅผ ์์ฑํ๊ธฐ ์ํ ๊ท์น์ด๋ ๊ฐ์ด๋๋ผ์ธ์ ์๋ฏธํ๋ค.
์๋๋ AngularJS Git Commit Message Conventions ์ ๋ฒ์ญํ๋ฉฐ ์ ๋ฆฌํ ๋ด์ฉ์ด๋ค.
์ปค๋ฐ ๋ฉ์์ง ํฌ๋งท
<type>(<scope>): <subject> # Subject Line
<BLANK LINE>
<body> # Message body
<BLANK LINE>
<footer> # Message footer- ์ด๋ค ๋ผ์ธ์ ์ปค๋ฐ ๋ฉ์์ง๋ค๋ 100๊ธ์ ์ด์์ ๋์ ์ ์๋ค. -> GitHUB๊ณผ ๊ฐ์ git tool์์ ์ฝ๊ธฐ ์ฌ์
Subject Line
- ์ ๋ชฉ ๋ผ์ธ์๋ ๋ณ๊ฒฝ์ฌํญ์ ๋ํ ๊ฐ๋จํ ์ค๋ช ์ด ํฌํจ๋์ด ์๋ค.
Allowed <type>
- feat : ๊ธฐ๋ฅ
- fix : ๋ฒ๊ทธ ์์
- docs : ๋ฌธ์ ์์
- style : ํฌ๋งทํ , ์ธ๋ฏธ์ฝ๋ก ์ถ๊ฐ...
- refactor : ๋ฆฌํฉํ ๋ง
- test : ๋๋ฝ๋ ํ ์คํธ ์ฝ๋ ์ถ๊ฐ
- chore : ๋น๋ ์ ๋ฌด ์์ , ํจํค์ง ๋งค๋์ ์
Allowed <scope>
- ์ค์ฝํ๋ commit์ ๋ณ๊ฒฝ์ฌํญ์ ๋ํ ๊ฒ์ ํฌํจํ๋ค.
- ex) $location, $browser, $compile, $rootScope, ngHref, ngClick, ngView, etc....
<subject> text
- ๋ช ๋ น๋ฌธ๊ณผ ํ์ฌ ์์ ๋ฅผ ์ฌ์ฉํจ : "changed" -> "change"
- ์ฒซ๊ธ์๋ฅผ ๋๋ฌธ์๋ก ์ฐ์ง ์๋๋ค.
- ๋ง์ง๋ง์ ์ (.)์ ์ ์ง ์๋๋ค.
Message body
- ๋ช ๋ น๋ฌธ๊ณผ ํ์ฌ ์์ ๋ฅผ ์ฌ์ฉํจ : "changed" -> "change"
- ์์ ์ ํ๊ฒ ๋ ์ด์ ์, ์ด์ ๋ณ๊ฒฝ์ฌํญ์ ๋ช ์ํ๋ค.
Message footer
"Breaking changes"
์ฃผ์ํ ๋ณ๊ฒฝ์ฌํญ์ footer์ ๋ณ๊ฒฝ์ ์ ์ค๋ช ๊ณผ ํจ๊ป ์ธ๊ธ๋์ด์ผ ํ๋ค.
๋ฌด์์ ๊ณ ์น๊ณ , ์ ์ํ๊ณ , ๋ง์ด๊ทธ๋ ์ด์ ํ๋์ง ์ ๋๋ค.
์์ )
BREAKING CHANGE: isolate scope bindings definition has changed and
the inject option for the directive controller injection was removed.
To migrate the code follow the example below:
Before:
scope: {
myAttr: 'attribute',
myBind: 'bind',
myExpression: 'expression',
myEval: 'evaluate',
myAccessor: 'accessor'
}
After:
scope: {
myAttr: '@',
myBind: '@',
myExpression: '&',
// myEval - usually not useful, but in cases where the expression is assignable, you can use '='
myAccessor: '=' // in directive's template change myAccessor() to myAccessor
}
The removed `inject` wasn't generaly useful for directives so there should be no code using it.
"Referencing issues"
ํด๊ฒฐ๋ ์ด์๋ footer์ ์์ฑํ๋ค.
"Closes" ํค์๋๋ก ์์ํ์ฌ ์์ฑํ๋ค.
Closes #234
/*์ฌ๋ฌ๊ฐ์ ์ด์์ ๊ฒฝ์ฐ์*/
Closes #123, #234, #994Examples
feat($browser): onUrlChange event (popstate/hashchange/polling)
Added new event to $browser:
- forward popstate event if available
- forward hashchange event if popstate not available
- do polling when neither popstate nor hashchange available
Breaks $browser.onHashChange, which was removed (use onUrlChange instead)fix($compile): couple of unit tests for IE9
Older IEs serialize html uppercased, but IE9 does not...
Would be better to expect case insensitive, unfortunately jasmine does
not allow to user regexps for throw expectations.
Closes #392
Breaks foo.bar api, foo.baz should be used insteadfeat(directive): ng:disabled, ng:checked, ng:multiple, ng:readonly, ng:selected
New directives for proper binding these attributes in older browsers (IE).
Added coresponding description, live examples and e2e tests.
Closes #351style($location): add couple of missing semi colonsdocs(guide): updated fixed docs from Google Docs
Couple of typos fixed:
- indentation
- batchLogbatchLog -> batchLog
- start periodic checking
- missing bracefeat($compile): simplify isolate scope bindings
Changed the isolate scope binding options to:
- @attr - attribute binding (including interpolation)
- =model - by-directional model binding
- &expr - expression execution binding
This change simplifies the terminology as well as
number of choices available to the developer. It
also supports local name aliasing from the parent.
BREAKING CHANGE: isolate scope bindings definition has changed and
the inject option for the directive controller injection was removed.
To migrate the code follow the example below:
Before:
scope: {
myAttr: 'attribute',
myBind: 'bind',
myExpression: 'expression',
myEval: 'evaluate',
myAccessor: 'accessor'
}
After:
scope: {
myAttr: '@',
myBind: '@',
myExpression: '&',
// myEval - usually not useful, but in cases where the expression is assignable, you can use '='
myAccessor: '=' // in directive's template change myAccessor() to myAccessor
}
The removed `inject` wasn't generaly useful for directives so there should be no code using it.
