Skip to content

UX improvements, #PG-5232#52

Open
lachiebol wants to merge 7 commits into
5.x-devfrom
PG-5232-UX-improvements
Open

UX improvements, #PG-5232#52
lachiebol wants to merge 7 commits into
5.x-devfrom
PG-5232-UX-improvements

Conversation

@lachiebol
Copy link
Copy Markdown
Contributor

@lachiebol lachiebol commented May 29, 2026

Description

  • Improved wording for token popup
  • Made try it out responses more clear by highlighting section
  • Changed wording on authorise button
  • Changed text on authorise button when connected
  • Cleaned up example input CSS (better disabled field feel & standard backgrounds)

Issue No

Steps to Replicate the Issue

Checklist

  • [✔/✖] Tested locally or on demo2/demo3?
  • [✔/✖/NA] New test case added/updated?
  • [✔/✖/NA] Are all newly added texts included via translation?
  • [✔/✖/NA] Are text sanitized properly? (Eg use of v-text v/s v-html for vue)
  • [✔/✖/NA] Version bumped?
  • [✔/✖/NA] Documentation updated?

@lachiebol lachiebol requested a review from AltamashShaikh May 29, 2026 02:51
@lachiebol lachiebol added the Needs Review For pull requests that need a code review. label May 29, 2026
@lachiebol lachiebol changed the title UX improvements UX improvements, #PG-5232 May 29, 2026
Comment thread lang/en.json Outdated
"ReportingApiMoreInformation": "More info about the Matomo APIs available in %1$sIntroduction to Matomo API%2$s and the %3$sMatomo API Reference%4$s.",
"ReportingApiReference": "Reporting API Reference",
"ReportingApiSummary": "All the data in Matomo is available through simple APIs.",
"SwaggerPageConnectToken": "Connect your Matomo API token",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be "Add your Matomo API token" ?
If this is given by Gillian, good to add

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gillian suggested 'Authenticate with a Matomo API token' Will go with that

Copy link
Copy Markdown
Contributor

@AltamashShaikh AltamashShaikh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lachiebol LGTM overall, but this looks like a valid concern, can you check

High-Risk Issues Blocking

  Annotations/GlobalApiComponents.php:18 changes the OpenAPI security scheme id from MatomoToken to Matomo API token, and Annotations/GlobalApiComponents.php:36 uses the same spaced name as the
  component key. OpenAPI component keys are expected to be identifier-like keys, not user-facing labels with spaces. The fixture now contains "Matomo API token" under components.securitySchemes, so
  generated specs become invalid or at least less interoperable for validators/codegen tooling. Keep the scheme id stable, e.g. MatomoToken, and put the user-facing copy in description or UI-layer
  text.

@lachiebol
Copy link
Copy Markdown
Contributor Author

@lachiebol LGTM overall, but this looks like a valid concern, can you check

High-Risk Issues Blocking

  Annotations/GlobalApiComponents.php:18 changes the OpenAPI security scheme id from MatomoToken to Matomo API token, and Annotations/GlobalApiComponents.php:36 uses the same spaced name as the
  component key. OpenAPI component keys are expected to be identifier-like keys, not user-facing labels with spaces. The fixture now contains "Matomo API token" under components.securitySchemes, so
  generated specs become invalid or at least less interoperable for validators/codegen tooling. Keep the scheme id stable, e.g. MatomoToken, and put the user-facing copy in description or UI-layer
  text.

I'll just revert this, I don't think it's impacting UX too much. The description change is probably enough here

@lachiebol lachiebol requested a review from AltamashShaikh June 1, 2026 21:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Needs Review For pull requests that need a code review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants