Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
11 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
b7563aa
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.
I realy wondering why autor of this mail had problem with replace(), but not with before() and after()?
A.before(B) << how did they deducated what must be done here? A set before B or B before A (without reading the spec?)
Personally I don't like this change, all this new methods was short and clear enought, but now you put one longer and boom...camelCases. The only plus is that some other lib use this new name, but in practice I still prefer shorter name.
b7563aa
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.
In general I recommend filing issues rather than commenting on commits. The reason we changed the name here is because these names were inspired by existing libraries, that do use
after()
/before()
, but notreplace()
.