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

IGVF-DACC / igvf-ui / #5540
100%
main: 100%

Build:
Build:
LAST BUILD BRANCH: IGVF-3031-pipeline-status-embed
DEFAULT BRANCH: main
Ran 25 Apr 2025 03:39AM UTC
Jobs 1
Files 161
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

25 Apr 2025 03:35AM UTC coverage: 100.0%. Remained the same
#5540

push

web-flow
IGVF-2277 Add file size facet (#764)

* First adaptation of example code. Not functional, no legend, and temporarily on the home page.
* Range selector now functions and appears correctly.
* Update variable names and comments, and add properties to `<RangeSelector>` on the way to an API for the component.
* Simplify the mechanism, merging the function to update the values into the function to update the range controls.
* Update comments.
* Handle fractional values for the range inputs. Set the initial values for the range inputs.
* Update a comment.
* Add range-selector facet type for MPRA quality metrics facets. Change the types of facet terms to either be an array or unknown because stats facets show `terms` can have any type.
* Work with both fractional and integer values. Consider only working with integers in the next commit, and the client has to multiply the values for display and actual usage.
* The `<RangeSelector>` component now only works with integers, and the client has to scale numbers to integers for the range selector, and scale them back for usage.
* Correct initial minimum and maximum values in the stats selector facet.
* Update the styling of the stats selector and legend.
* Finish the styling of the stats facet.
* Add non-functioning buttons for resetting and actuating the stats range facet. Add icon for reset.
* Update facet files to handle facet terms with a potentially unknown term type.
* Range selector now sensitive to current relevant query-string elements. Still has a bug where resetting the range doesn’t affect the sliders. Will address that in the next commit.
* The range selectors now respond to relevant query string elements. `<RangeSelector>` no longer maintains its own state, instead receiving its state from the parent component.
* Reset the range sliders when resetting the range.
* Fix build error in the last commit.
* Fix how I handle changes to stats.min and stats.max so that the range updates correctly.
* Disable r... (continued)

1341 of 1341 branches covered (100.0%)

Branch coverage included in aggregate %.

161 of 161 new or added lines in 9 files covered. (100.0%)

3053 of 3053 relevant lines covered (100.0%)

17.65 hits per line

Jobs
ID Job ID Ran Files Coverage
1 #5540.1 25 Apr 2025 03:39AM UTC 161
100.0
Source Files on build #5540
  • Tree
  • List 161
  • Changed 8
  • Source Changed 0
  • Coverage Changed 8
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • 68050434 on github
  • Prev Build on dev
  • Next Build on dev
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc