Describe the bug
When an opacity modifier value on a token is updated, the change is correctly saved to the JSON and shown in the plugin view, but is not detected by the GitHub sync feature. The diff tab shows no changes, preventing the change from being committed to the repository.
Reproduced on multiple computers and multiple accounts — other token changes sync correctly, so the issue appears specific to opacity modifier values.
To Reproduce
- Open the plugin and select a token with an opacity modifier
- Change the opacity modifier value (e.g., to
0.35)
- Save — the value updates correctly in the plugin view
- Click the sync button
- Select the diff tab
Expected behavior
The diff tab should show the changed opacity modifier value as a pending change ready to commit.
Actual behavior
The diff tab shows no changes at all, even though the value has been updated locally.
Open questions / next steps
Screenshots or Screencasts
Screenshots were shared by the customer but are not available to attach here.
Additional context
- Reported via customer support (HubSpot ticket #418657485039)
- Reproduced on multiple machines and multiple accounts
- Other token changes (non-opacity) sync correctly
Describe the bug
When an opacity modifier value on a token is updated, the change is correctly saved to the JSON and shown in the plugin view, but is not detected by the GitHub sync feature. The diff tab shows no changes, preventing the change from being committed to the repository.
Reproduced on multiple computers and multiple accounts — other token changes sync correctly, so the issue appears specific to opacity modifier values.
To Reproduce
0.35)Expected behavior
The diff tab should show the changed opacity modifier value as a pending change ready to commit.
Actual behavior
The diff tab shows no changes at all, even though the value has been updated locally.
Open questions / next steps
Screenshots or Screencasts
Screenshots were shared by the customer but are not available to attach here.
Additional context