686f846fa5
This adds a check that triggers an error if Select2 was not able to detect a copy of jQuery on the page. This should help users when they are setting up Select2. **Breaking change:** The full build no longer includes jQuery. Previously, the full build included all requirements for Select2, including jQuery, which meant that anyone looking for the optional requirements had to possibly include multiple versions of jQuery on their page. This means that anyone requiring Select2 to also bundle jQuery will now need to include jQuery on their pages alongside Select2. A copy of jQuery is included in the repository. **Breaking change:** The AMD build of Select2 will now correctly wrap the code in a `define` block. It will still create the named blocks inside of the code, which should be valid in most AMD build systems, so now Select2 is compatible with cases where the file does not have the same name as the Select2 module name. **Breaking change:** Select2 will re-use the AMD methods if they are available on the page, but it will not longer leak the included AMD loader to the global scope. The AMD methods will still be available on the `jQuery.fn.select2.amd` namespace. The `mock.js` test file has been renamed to `helpers.js` and will handle the escalation of the `require` and `define` variables to the global scope. It should be included in all test files, or the tests will fail. This closes https://github.com/select2/select2/issues/2946.
Select2 Documentation
This repository holds the latest documentation for Select2.
What is this?
The documentation is automatically extracted from the docs directory at the
Select2 source repository. This is done periodically by
the maintainers of Select2.
Pull requests will usually be ignored, documentation fixes should be made in
the source repository. We may accept pull requests if they match the
source docs directory, but for the most part pull requests will be closed on
sight.
How can I build these docs manually?
In the main Select2 repository, you can build the documentation by executing
grunt docs
Which will start up the documentation on port 4000. You will need Jekyll installed to build the documentation.