ACTION-14: Change naming scheme to use a "createX" approach rather than just "X"
Change naming scheme to use a "createX" approach rather than just "X"
- State:
- closed
- Person:
- Ryan Sleevi
- Due on:
- September 10, 2012
- Created on:
- July 24, 2012
- Associated Issue:
- ISSUE-37
- Related emails:
- W3C Web Crypto WG - Take Away from 17th of september call (from Virginie.GALINDO@gemalto.com on 2012-09-18)
- [minutes] Re: W3C Web Crypto WG - agenda for 17th of september call - today (from wseltzer@w3.org on 2012-09-17)
- Web Crypto WG - ACTION-14 associated with ISSUE-37 (from Virginie.GALINDO@gemalto.com on 2012-08-31)
- crypto-ISSUE-37: Method naming [Web Cryptography API] (from sysbot+tracker@w3.org on 2012-08-29)
- Re: crypto-ISSUE-37: Method naming [Web Cryptography API] (from sleevi@google.com on 2012-08-28)
Related notes:
[hhalpin]: Change naming scheme to use a "createX" approach rather than just "X"
13 Aug 2012, 19:12:16[hhalpin]: [CONTINUES]
13 Aug 2012, 19:13:44Renamed methods to be createVerb-er form in r1.15 of Overview.html
However, this proposal highlights the original motivation for "simple" verbs such as "encrypt". The question as to what the correct spelling is - createEncrypter vs createEncryptor (both of which can be seen as valid spellings) - is something that will likely trip up more developers than .encrypt() may have.
This action is postponed after the FPWD.
Virginie GALINDO, 31 Aug 2012, 15:23:21Display change log.