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

solidjs / solid / 34574896189
79%
main: 79%

Build:
Build:
LAST BUILD BRANCH: claude/project-thread-ln9xkt
DEFAULT BRANCH: main
Ran 11 Sep 2026 07:38AM UTC
Jobs 1
Files 6
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

11 Sep 2026 07:32AM UTC coverage: 71.842%. Remained the same
34574896189

push

github

web-flow
fix(compiler): name server functions by their binding path (#3363)

* fix(compiler): name server functions by their binding path

Server-function ids used the nearest binding name alone, so two functions
with the same name in one file were told apart by a positional ordinal
assigned in traversal order. Appending a third same-named function
renumbered the other two and re-pointed addresses a deployed client was
still holding, which is the mis-dispatch #3109 set out to remove.

- The descriptive name is now the function's dotted binding path, so
  `makeA.submit` and `makeB.submit` are two names instead of one name and a
  counter.
- Object property keys, class names, and class member keys contribute path
  segments too, so `handlers.save` and `Api.refresh` name themselves.
- A key that is not identifier-shaped contributes no segment, keeping `-`
  and `.` out of the name so `id.split("-")[1]` stays the file hash.
- The ordinal remains only for two functions that share one path, such as
  two inline callbacks in the same scope.

Ids move once for nested server functions. The frozen Babel reference files
for the three affected fixtures were edited by hand, id literals only.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* fix(compiler): a named function contributes its own path segment

A function expression passed straight to a call has no binding of its
own, so with the container alone naming it, two of them in one scope
fell back to the positional ordinal the path was introduced to remove:
`register(function saveHandler() {})` beside `dropHandler` inside
`wire` became `wire` and `wire-1`. A function declaration nested in
another function is not bubbled into a const either, so it contributed
no segment and same-named arrows in sibling declarations collided too.

A named function is now a named container like the others. Its name is
skipped only when it repeats the segment already on the path, so a
bubbled `const makeA = function ma... (continued)

519 of 790 branches covered (65.7%)

Branch coverage included in aggregate %.

772 of 1007 relevant lines covered (76.66%)

15.02 hits per line

Jobs
ID Job ID Ran Files Coverage
1 34574896189.1 11 Sep 2026 07:38AM UTC 6
71.84
GitHub Action Run
Source Files on build 34574896189
  • Tree
  • List 6
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #34574896189
  • c0299bf4 on github
  • Prev Build on next (#34574334058)
  • Next Build on next (#34574929185)
  • Delete
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