01e2bd5050
The Pivotal copyright notice needs to be retained. That's the right thing to do and the MIT license requires it. However, using it by itself becomes more obviously incorrect with each passing year since Pivotal ceased to exist. Moreover, Pivotal hasn't actually been the sole copyright owner since the first external contribution was merged. Contributors were not asked to sign a copyright assignment, so they retain copyright to their contributions. "Copyright (c) 2008-2019 Pivotal Labs" complies with the terms of the license and acknowledges Pivotal's outsized role in developing Jasmine. "Copyright (c) 2008-$YEAR The Jasmine developers" acknowledges all authors and will remain correct in the future.
66 lines
2.7 KiB
JavaScript
66 lines
2.7 KiB
JavaScript
/*
|
|
Copyright (c) 2008-2019 Pivotal Labs
|
|
Copyright (c) 2008-2023 The Jasmine developers
|
|
|
|
Permission is hereby granted, free of charge, to any person obtaining
|
|
a copy of this software and associated documentation files (the
|
|
"Software"), to deal in the Software without restriction, including
|
|
without limitation the rights to use, copy, modify, merge, publish,
|
|
distribute, sublicense, and/or sell copies of the Software, and to
|
|
permit persons to whom the Software is furnished to do so, subject to
|
|
the following conditions:
|
|
|
|
The above copyright notice and this permission notice shall be
|
|
included in all copies or substantial portions of the Software.
|
|
|
|
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
|
|
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
|
|
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
|
|
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
|
|
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
|
|
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
|
|
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
|
|
*/
|
|
/**
|
|
This file starts the process of "booting" Jasmine. It initializes Jasmine,
|
|
makes its globals available, and creates the env. This file should be loaded
|
|
after `jasmine.js` and `jasmine_html.js`, but before `boot1.js` or any project
|
|
source files or spec files are loaded.
|
|
*/
|
|
(function() {
|
|
const jasmineRequire = window.jasmineRequire || require('./jasmine.js');
|
|
|
|
/**
|
|
* ## Require & Instantiate
|
|
*
|
|
* Require Jasmine's core files. Specifically, this requires and attaches all of Jasmine's code to the `jasmine` reference.
|
|
*/
|
|
const jasmine = jasmineRequire.core(jasmineRequire),
|
|
global = jasmine.getGlobal();
|
|
global.jasmine = jasmine;
|
|
|
|
/**
|
|
* Since this is being run in a browser and the results should populate to an HTML page, require the HTML-specific Jasmine code, injecting the same reference.
|
|
*/
|
|
jasmineRequire.html(jasmine);
|
|
|
|
/**
|
|
* Create the Jasmine environment. This is used to run all specs in a project.
|
|
*/
|
|
const env = jasmine.getEnv();
|
|
|
|
/**
|
|
* ## The Global Interface
|
|
*
|
|
* Build up the functions that will be exposed as the Jasmine public interface. A project can customize, rename or alias any of these functions as desired, provided the implementation remains unchanged.
|
|
*/
|
|
const jasmineInterface = jasmineRequire.interface(jasmine, env);
|
|
|
|
/**
|
|
* Add all of the Jasmine global/public interface to the global scope, so a project can use the public interface directly. For example, calling `describe` in specs instead of `jasmine.getEnv().describe`.
|
|
*/
|
|
for (const property in jasmineInterface) {
|
|
global[property] = jasmineInterface[property];
|
|
}
|
|
})();
|