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

lotus / assets / 54 / 8
97%
master: 97%

Build:
Build:
LAST BUILD BRANCH: v0.1.0
DEFAULT BRANCH: master
Ran 24 Oct 2015 02:45PM UTC
Files 11
Run time 0s
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

24 Oct 2015 02:37PM UTC coverage: 99.003%. First build
2.1.6

push

travis-ci

jodosha
Unified asset sources.

On before each asset type (javascript, stylesheet) used to have its own
definition of sources. That was repetitive to configure and didn't
matched real use cases.

We went from:

  Lotus::Assets.configure do
    # ...
    define(:javascript) do
      sources << [
        'assets',
        'vendor/assets/bootstrap/javascripts'
      ]
    end

    define(:stylesheet) do
      sources << [
        'assets',
        'vendor/assets/bootstrap/stylesheets'
      ]
    end
  end

To this:

  Lotus::Assets.configure do
    sources << [
      'assets',
      'vendor/assets/bootstrap'
    ]
  end

This DRY configuration has another win: it lets devs to load all the
files defined under a source, without worrying about the asset type.
For instance Bootstrap ships with fonts and images that we want to
serve without the need of manually configure this kind of assets.

298 of 301 relevant lines covered (99.0%)

29.84 hits per line

Source Files on job 54.8 (2.1.6)
  • Tree
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 54
  • Travis Job 54.8
  • f08fb5e4 on github
  • Next Job for 2.1.6 on deployment (#55.8)
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

© 2025 Coveralls, Inc