Releases: cthae/Adobe-Launch-Debugger
Releases · cthae/Adobe-Launch-Debugger
Release 1.21.1
Chrome: https://chromewebstore.google.com/detail/universal-adobe-debugger/ehadnibhemgjphdjgkallndphbghlpkn?hl=en-US
Firefox: https://addons.mozilla.org/en-CA/firefox/addon/universal-adobe-debugger/
Changelog:
- Add the onActivated listener for smoother favicon and setdebug reevaluation.
- Release v1.21 to Chrome and FF.
- Change the extension icon depending on the env:
- grey for when the extension hasn't yet executed all code or doesn't have the permission to do so;
- green indicates that the Launch env is production;
- yellow indicates that the Launch env is dev or staging;
- red indicates that the Launch library is not loaded or loaded incompletely. Basically, _satellite?.environment?.stage is falsy. The rest of the functionality won't be stopped by this, however.
- Update the extension icon.
- Disable Launch UI improvements on by default.
- Release v1.20.3 to Chrome
- Appmeasurement: fix e# custom logging. Refactor custom events logging.
- Appmeasurement: URL decode values of variables in custom logging.
- Release v1.20.2 to Chrome and FF
- Allow ampersands.
- Release v1.20.1 to Chrome
- Fix the custom logging prop detection regex.
Release 1.20
Chrome: https://chromewebstore.google.com/detail/universal-adobe-debugger/ehadnibhemgjphdjgkallndphbghlpkn?hl=en-US
Firefox: https://addons.mozilla.org/en-CA/firefox/addon/universal-adobe-debugger/
Changelog:
- Add onInstalled/onStartup callbacks to set the default set of settings specifically for those who don't open the popup after installation.
- Support for Mozilla FF. Same extension. Cross-browsers. Seems like mostly only background will have to be reimplemented, but many APIs may be off. We'll see.
Release 1.10
- Appmeasurement: Prettify the product string printing.
- Appmeasurement: Add transaction id in the product string prettifier.
- Implement Launch UI improvements POC:
- Launch UI: Add the red indicator whenever a lib is not selected.
- Launch UI: Add a hint about how to change the Launch UI via Chrome flags.
- Add an option to print general alloy config in the snippets tab. Make sure it does so for all Alloy instances.
Release 1.09.50
- Rename the content-script.js to something more interesting. It's visible in the console and can be filtered by.
- Web SDK: Further improve the custom logging, allowing shorthands: p12/c12/v12/e12/l2.
- Apply all the shorthanded custom logging to Appmeasurement logging too.
- Release v1.09.1 To the webstore only.
- Fix a bug in custom logging, in event shortcuts for the data.__adobe.analytics usecases.
- Fix a bug in custom logging, in prop shortcuts for the data.__adobe.analytics usecases.
Release 1.09
- Web SDK: Expose the event type in the logging header.
- Web SDK: Improve the custom logger to also check the data.__adobe.analytics object when using shortcuts.
- Web SDK: Make it easier for non-technical people to use the custom logging: don't require them to specify the full path to evars, props or events for xdm payloads. If users ask for evars and it's an xdm event, just add the correct path to it.
- Reimplement page load time to something like performance.getEntriesByType("navigation")[0]?.duration
Release 1.08
- Web SDK: On errors, in custom logs, add an indication that the request resulted in an error. This is for people who use filters in the console like pros. Thanks Arun for noticing.
- Web SDK: MVP tracking the navigator.sendBeacon() ping network requests. No access to their payloads, however, because the Chrome devteam neglects fixing related bugs.
- Delete requests from the map on other callbacks too to avoid misreporting calls as such that didn't receive the server response.
- v1.07.1: increase the timeout limit from 1 to 2 seconds.
Release 1.07
- Print the extension version, getting it from the manifest.
- UX improvements, CSS fixes.
- Add a bug submission button in info.
- Web SDK: Add an option to log all fields there are, giving the user the raw object.
- Add a callback and error logging for "cancelled" requests. That's when the browser cancels the request. And a few other types of requests. Thanks to Arun for the suggestion.
- Web SDK: Apply the error logging logic to Web SDK tracking too
- Small popup UI improvements.
Release 1.06 - Byanka
1.06 (Byanka's Web SDK improvements update)
- Replace the counter of PVs and links with AA calls and WebSDK calls
- Web SDK: Improve autodebugging: indicate when linkClicks will be treated as pageviews in AA due to the web fields set.
- Web SDK: Surface the Edge config ids for every request, make them visible just like AA Report Suites. To ease the debugging of multi-destinational tracking. First 5 characters should suffice.
- Web SDK: Improve the tracking of network errors when edge network requests fail.
- Web SDK: Refactor logging. Make it less confusing. No more nested groups.
- Web SDK: Change the default logging a bit to maybe try and expand the analytics object automatically.
- Web SDK: Add a setting to remove the essentially useless xdm fields that are rarely useful to look at. On by default.
- Web SDK: Improve the logging for non-object fields.
- Web SDK: Add logging for the data.__adobe object. Off by default in settings.
- Web SDK: Reinforce the custom logging field, allow people to use the xdm. reference in the list of params.
Release 1.05
1.05
- QOL Improvements for the custom web SDK logging.
- Allow the underscore in the field names.
- Small reporting improvements.
1.04
- Configure selective logging for the web SDK.
Release 1.03
- CSS improvements of the extension popup. Thanks Chip!
- Fix a bug in the new custom logging code.
- Add a line to indicate the end of the main logging group for easier reading.