[[ Breaking Changes ]] Update for implicit object changes

montegoulding · montegoulding · commit 2c1029f51cb4 · 2019-05-15T10:32:43.000+10:00
This patch adds a note about the change to the implicit object in widget
handlers introduced in this release.
diff --git a/docs/notes-base/breaking_changes.md b/docs/notes-base/breaking_changes.md
@@ -40,3 +40,25 @@ The constant `infinity` has been added to the language in this release. As a
 result, the unquoted literal `infinity` is now reserved. Any existing uses
 of it should be quoted, as otherwise it will resolve to the floating point
 value representing infinity, rather than the string "infinity".
+
+## Implicit object
+
+A number of LCB commands use an implicit object to provide context for their
+execution. Some of these commands also allow specifying an explicit object.
+These commands are:
+
+- `execute script`
+- `send`
+- `post`
+- `image from file`
+- `resolve file` - new in this version
+
+In previous releases `execute script` and `image from file` would use
+`this card of the defaultStack` as the implicit object even if called from
+a widget. The `send` and `post` commands, however, used
+`this card of the defaultStack` when in a library module handler and the host
+widget when in a widget module handler. This release changes `execute script`
+and `image from file` to also use the host widget as the implicit object. This
+means, for example, that `image from file` will resolve a relative file path
+relative to the `stackFile` the host widget is on rather than the `stackFile` of
+the `defaultStack`.
