- Suggest `<script>` tags sourcing inlay bundles now specify `type=module`. This
should not hurt existing scripts but might be important to support ESM modules used within scripts.
## 1.3.3
...
...
@@ -13,7 +15,7 @@
## 1.3.2
- Fix [issue #10](https://lab.civicrm.org/extensions/inlay/-/issues/10) - CORS errors if inlay used on same domain as CiviCRM.
- There’s now a simple preview page to be able to see how an inlay might look/work before placing it on another site. It’s a good idea to test on the site you’re actually wanting to use it on, but this will have its uses. Click the new *Preview* link from the inlays list. [Enhanement #8](https://lab.civicrm.org/extensions/inlay/-/issues/8)
- There’s now a simple preview page to be able to see how an inlay might look/work before placing it on another site. It’s a good idea to test on the site you’re actually wanting to use it on, but this will have its uses. Click the new _Preview_ link from the inlays list. [Enhanement #8](https://lab.civicrm.org/extensions/inlay/-/issues/8)
## 1.3.1
...
...
@@ -21,7 +23,6 @@
- Allow inlays to boot up immediately if the page has already completed loading. This is not the usual case, but is the case when another script adds in an Inlay script.
- You can now see console debug messages by calling `localStorage.setItem('inlayDebug', 1)` To disable: `localStorage.removeItem('inlayDebug)` Other inlay scripts may wish to use `CiviCRMInlay.debug()` to pass debug messages, instead of console.log
## 1.3.0 Type hints
More type hints have been added to the `\Civi\Inlay\Type` class. Inlays whose method signatures do not match these will hit trouble - update your code and test! (Hence the minor version jump.)
