-
Notifications
You must be signed in to change notification settings - Fork 405
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Conflicts: build/js/messenger.js build/js/messenger.min.js package.json
- Loading branch information
Showing
5 changed files
with
58 additions
and
28 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,34 +1,45 @@ | ||
1.2.2 | ||
----- | ||
|
||
- Message strings (as opposed to full objects) can now be passed into message.update. | ||
|
||
1.2.1 | ||
----- | ||
|
||
- Added `ajax` alias for `run` with `$.ajax` as the action. This is essentially identical | ||
to the default behavior, but is useful to those who wish to be more explicit. | ||
|
||
1.2.0 | ||
----- | ||
|
||
Added global Messenger object which can be removed with `Messenger.noConflict()`. The | ||
Messenger object will provide a container other than the jQuery object for messenger | ||
externals. | ||
- Added global Messenger object which can be removed with `Messenger.noConflict()`. The | ||
Messenger object will provide a container other than the jQuery object for messenger | ||
externals. | ||
|
||
Messenger may also be called to provide the same functionality as `$.globalMessenger`. | ||
- Messenger may also be called to provide the same functionality as `$.globalMessenger`. | ||
|
||
Messenger default options may now be set on `window.Messenger.options` as well as | ||
`$._messengerDefaults`. | ||
- Messenger default options may now be set on `window.Messenger.options` as well as | ||
`$._messengerDefaults`. | ||
|
||
The current instance of ActionMessenger which will be used by Messenger()/$.globalMessenger | ||
calls is now accessable as `window.Messenger.instance`, not `$._messengerInstance`. | ||
- The current instance of ActionMessenger which will be used by `Messenger()`/`$.globalMessenger` | ||
calls is now accessable as `window.Messenger.instance`, not `$._messengerInstance`. | ||
|
||
Added `run` alias for `go`. This change makes it easier for developers writing js. | ||
In JavaScript, go, being a reserved word, always had to be referenced using array | ||
notation, this provides a way around that limitation. | ||
- Added `run` alias for `go`. This change makes it easier for developers writing js. | ||
In JavaScript, go, being a reserved word, always had to be referenced using array | ||
notation, this provides a way around that limitation. | ||
|
||
Created common way for themes to define extra JavaScript. Themes can now define their | ||
own Messenger and/or Message objects in the `window.Messenger.themes.<theme_name>` object. | ||
If the theme name is provided in the options to globalMessenger as `options.theme`, the | ||
defined classes will be used. As the theme now has to be passed in as a seperate option, the | ||
`messenger-theme-x` class will now be automatically added, and does not need to be | ||
provided in extraClasses. | ||
- Created common way for themes to define extra JavaScript. Themes can now define their | ||
own Messenger and/or Message objects in the `window.Messenger.themes.<theme_name>` object. | ||
If the theme name is provided in the options to globalMessenger as `options.theme`, the | ||
defined classes will be used. As the theme now has to be passed in as a seperate option, the | ||
`messenger-theme-x` class will now be automatically added, and does not need to be | ||
provided in extraClasses. | ||
|
||
MagicMessage has been renamed RetryingMessage. | ||
- `MagicMessage` has been renamed `RetryingMessage`. | ||
|
||
The base classes Message and Messenger have been renamed _Message and _Messenger to | ||
signify that they are only for the internal structuring of the code, and not expected | ||
to be used directly. | ||
- The base classes `Message` and `Messenger` have been renamed `_Message` and `_Messenger` to | ||
signify that they are only for the internal structuring of the code, and not expected | ||
to be used directly. | ||
|
||
Messenger now exposes ActionMessenger (as Messenger) and RetryingMessage (as Message) for | ||
use by theme which wish to extend them. | ||
- Messenger now exposes `ActionMessenger` (as `Messenger`) and `RetryingMessage` (as `Message`) for | ||
use by theme which wish to extend them. |
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
Large diffs are not rendered by default.
Oops, something went wrong.
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
66f377e
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.
Merge branch
master
into gh-pa
Conflicts: build/js/messenger.js build/js/messenger.min.js package.json