• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

hyperglass-community / hyperglass / 44919825075
87%

Build:
DEFAULT BRANCH: main
Ran 21 Nov 2026 03:34PM UTC
Jobs 2
Files 441
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

21 Nov 2026 03:33PM UTC coverage: 86.194% (+0.04%) from 86.156%
44919825075

push

github

web-flow
fix(ui): keep the query form consistent after location changes and resets (#545)

* fix(ui): clear a query type the selected locations don't offer

A location change kept the query type in the form values and the select
when the new locations no longer offered it. Clear it with its target and
variables, as choosing another query type does. When the new locations
offer the same query type under another ID (directives are intersected by
name and the first location's IDs are offered), follow it to that ID and
keep the target.

* fix(ui): clear the target when the only query type is chosen for you

When the selected locations have one query type in common and it isn't
the current one, locationChange chose it but kept the target, while a
manual query type change clears it. Clear the target and its display
too. A query type that stays the same keeps its target.

* fix(ui): clear validation errors when the form is reset

A reset from the header title cleared the store and, through the mirror,
react-hook-form's values, but not its errors: an error shown before the
reset stayed on screen, and a target error came back with the next query.
When the store's values are back to the empty ones, reset react-hook-form
instead of setting its values, so its errors and submitted state go too.
The mirror reads the store's values object by reference, so it also runs
when a reset replaces values that were already empty.

* fix(ui): drop values a same-named query type doesn't offer

When removing a location moves the query type to a directive with the
same name and another ID, the target and variables were kept as they
were. Two custom directives can share a name and nothing else, so a
variable the new directive doesn't define stayed in the store, unseen,
and the query was rejected with "Unknown variable".

Keep only the variables (and values) the new directive defines and
offers. Keep the target only when the new directive takes the same kind
of target and, for a select, of... (continued)

495 of 778 branches covered (63.62%)

Branch coverage included in aggregate %.

33 of 33 new or added lines in 3 files covered. (100.0%)

17904 of 20568 relevant lines covered (87.05%)

10.68 hits per line

Jobs
ID Job ID Ran Files Coverage
1 frontend - 44919825075.1 21 Nov 2026 03:34PM UTC 124
72.37
GitHub Action Run
2 backend - 44919825075.2 21 Nov 2026 03:37PM UTC 317
88.2
GitHub Action Run
Source Files on build 44919825075
  • Tree
  • List 441
  • Changed 3
  • Source Changed 3
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #44919825075
  • 07fb9b51 on github
  • Prev Build on main (#44919324370)
  • Next Build on main (#44922130797)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc