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

RefreshOptions: Add truthiness check when sorting optgroups with lockOptgroupOrder #1163

Closed
wants to merge 50 commits into from

Conversation

bwilson-ux
Copy link
Contributor

When using 'lockOptgroupOrder' - if b is not defined it throws an error breaking the component. This change fixes this issue by checking whether it has something to compare first before trying to get access to the object property.

When using 'lockOptgroupOrder' - if b is not defined it throws an error breaking the component. This change fixes this issue by checking whether it has something to compare first before trying to get access to the object property.
@joallard
Copy link
Member

Oops, you changed dist!

Same update applied to the dist version.
@bwilson-ux
Copy link
Contributor Author

@joallard thanks for the heads up! I only updated dist to rectify my current issue not thinking about the actual build... Updated patch also 👍

@joallard
Copy link
Member

joallard commented Oct 3, 2016

Sorry to make you go back and forth on this, but there's no way to do this simply in the Github interface: can you rebase and remove your first commit, leaving just the changes to src/?

Otherwise I'm ready to merge as-is, it's trivial enough to be comprehendable.

@joallard joallard changed the title lockOptgroupOrder - Update RefreshOptions: Add truthiness check when sorting optgroups with lockOptgroupOrder Oct 3, 2016
parsonsmatt and others added 24 commits October 4, 2016 14:02
I attempted to use selectize.js with a `create: function(input, callback) {}` pattern, as suggested by the docs. This wouldn't work, as the function never returns anything.. After some light debugging, I realized that the `callback` function wasn't being used or defined. I tried setting up the function given in the example, and it worked. I checked some of the examples with this definition, and they all followed the given format.
Added information about default values and asynchronous function
Wasted a lot of time because triggerDropdown was not documented.
Use correct jQuery API to get option value
Fixes selectize#1016
Replacing jQuery for $
Closes selectize#785 [skip-ci]

- Some typo fixes
- Fixes selectize#779, selectize#745, selectize#464 and perhaps some others

(Markdown doesn't work inside tables :-( )
joallard and others added 24 commits October 4, 2016 14:02
- Correct tests
- Use hyphen instead of underscore in new node id
- tweak handling under iOS
- improve blur handling and add option
- improve pullrequest based on helpful feedback
- change CHANGELOG
Even though we still need to get a team on the ground
[skip ci]
Replaced reference to window.jQuery in removeHighlight plugin
Sometimes element passed as second argument to onBlur handler
doesn't have focus method, i.e. inline svg element in IE
When using 'lockOptgroupOrder' - if b is not defined it throws an error breaking the component. This change fixes this issue by checking whether it has something to compare first before trying to get access to the object property.
Same update applied to the dist version.
@github-actions
Copy link
Contributor

github-actions bot commented Jan 7, 2021

This pull request is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days

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

Successfully merging this pull request may close these issues.