Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

3.5 -> 4.0 migration notices #3483

Closed
kevin-brown opened this issue Jun 16, 2015 · 0 comments
Closed

3.5 -> 4.0 migration notices #3483

kevin-brown opened this issue Jun 16, 2015 · 0 comments

Comments

@kevin-brown
Copy link
Member

In order to make migrating to 4.0 easier, we are planning on adding the debug option to 3.5.3 which will display notices/warnings/errors when configurations are used that are not compatible with 4.0, or when options used have been renamed in 4.0.

@kevin-brown kevin-brown added this to the 3.5.3 milestone Jun 16, 2015
kevin-brown added a commit that referenced this issue Jun 29, 2015
The `debug` option was chosen because the option also exists in
Select2 4.0.0 and provides similar warnings when configurations
are detected that are known to cause issues in Select2.

Warnings will be displayed in the console if the debug option is
enabled. As there are a lot of options that have been renamed in
Select2 4.0.0, using the older version of the options will trigger
a warning in Select2 3.5.3. Options which were also removed and
have clear migration paths will also trigger a warning with the
link to the relevant documentation.

Options which have been renamed in Select2 4.0.0 are now supported
in Select2 3.5.3, allowing people to migrate their installations
over to the new options before making the final switch.

This closes #3483.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant