| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Remove leading comments that are just stating the filename.
Move any file-level comments below the copyright banner.
Remove leading blank lines.
|
| | |
|
| |
|
|
|
|
|
|
| |
We left the deleted update system in 3.6 to support upgrades from 3.4,
but newer versions will always use the new UpdateNode update system.
Fun fact: this commit deletes more lines than were inserted by the
previous 100 commits.
|
| |
|
|
|
|
|
|
|
| |
The $pushAll modifier was deprecated and is now unsupported. Clients
should switch to the $push modifier with $each to get $pushAll
behavior.
This patch also updates some copyright notices that should have been
updated as part of file renames in bf99c6.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A $rename is implemented with two UpdateLeafNode classes: RenameNode and
ConflictPlaceholderNode. The ConflictPlaceHolder node exists only to
mark the source path of the rename in the update tree, so that it
generates a conflict if another modifier tries to act on the same
path.
Actually writing the destination path and unsetting the source path
occurs in RenameNode apply method.
The RenameNode gets placed in the update tree according to its
destination path, so that when we reach the RenameNode apply method,
pathTaken and pathToCreate are with respect to the destination path,
allowing us to create the path if we need to.
|
| |
|
