abepetrillo / evergreen

99%

master: 99%

LAST BUILD ON BRANCH noConflict_require

branch: noConflict_require

CHANGE BRANCH

x

Reset

• noConflict_require
• 1.1.0
• 1.1.1
• 1.1.2
• 1.1.3
• 1.2.0
• ap-fix_run_all
• ap-fix_warnings
• ap-templates_in_folder
• ap-upgrade_phantomjs
• bump_version
• capybara_upgrade
• circleci-project-setup
• coverage
• fix_build
• fix_readme
• fix_serve_command
• master
• remove_need_for_rspec_its
• ruby_2
• switch_to_poltergeist
• update_rspec
• version_bump

Build # 76

Build Type

push

travis-ci

Committed by abepetrillo

Commit Message

Introduce noConflict for global JS methods

Attempting to support a noConflict option similar to jQuery's
noConflict. If Evergreen nukes a pre-existing method like `require`,
calling `Evergreen.noConflict()` will retrive the old definition, and
the developer is required to use `Evergreen.require` instead of `require`

The code is pretty crude, but any sort of refactor seems to upset
poltergeist, so I'll get to refactoring this later

This should satisfy issue #17.

Run Details

308 of 311 relevant lines covered (99.04%)

48.95 hits per line