Skip to content

Conversation

@acolchagoff
Copy link
Contributor

@acolchagoff acolchagoff commented Feb 15, 2017

I was trying to make an easy way for clients to copy and paste tags from a spreadsheet, but I was unable to do this because select2's use of a 'search' input would remove all newline characters from the pasted input. replacing the search text input with a textarea removes this limitation.

This pull request includes a

  • Bug fix
  • New feature

The following changes were made

Replaced <input type="search" /> with <textarea></textarea>

If this is related to an existing ticket, include a link to it as well.

I was trying to make an easy way for clients to copy and paste tags from a spreadsheet, but I was unable to do this because select2's use of a 'search' input would remove all newline characters from the pasted input. replacing the search text input with a textarea removes this limitation.
@acolchagoff
Copy link
Contributor Author

clearly this needs more work.

@acolchagoff acolchagoff force-pushed the master branch 2 times, most recently from 3b31347 to 7c6d350 Compare February 16, 2017 19:15
@acolchagoff
Copy link
Contributor Author

acolchagoff commented Jun 15, 2017

@kevin-brown Our company is running a fork of select2 in order to have this functionality, so I'm running this code in production without issue, What can I do to get this pr accepted so that I can get back to running the master trunk?

@acolchagoff
Copy link
Contributor Author

@alexweissman are you a new maintainer? what do I need to do to get this in?

@alexweissman
Copy link
Contributor

I'm a "maintainer-in-training". My main goal is to improve the documentation and get the obvious bug fixes merged in.

This looks like a good feature, but it has the potential to create breaking changes for anyone who is expecting an input field. Can we make this a configuration option instead? Maybe something like searchElement that can take on a value of either input (default) or textarea?

@acolchagoff
Copy link
Contributor Author

sounds good, I'll get to work.

@acolchagoff
Copy link
Contributor Author

@alexweissman I've sorted this out and written the change to config. The code passes tests and I've tested this in our environment. if searchElement = 'textarea' a textarea will be used, otherwise an input will be used as usual, so this should not change backward compatibility.

acolchagoff pushed a commit to select2/docs that referenced this pull request Feb 20, 2019
@acolchagoff
Copy link
Contributor Author

documentation pull request here: select2/docs#27

@kevin-brown
Copy link
Member

Unfortunately this pull request contains files in the dist folder, and as a result there is a merge conflict.

If you are still interested in making this contribution, feel free to remove the dist changes from this pull request and leave a comment asking for this to be re-reviewed.

@acolchagoff
Copy link
Contributor Author

@kevin-brown I've done this, how does it look now?

@acolchagoff
Copy link
Contributor Author

@kevin-brown @alexweissman Just pinging this again, can I merge it in?

@kevin-brown
Copy link
Member

Is there a reason why we wouldn't just switch it to always use a <textarea> instead of giving the option of both? (aside from backwards compatibility reasons)

@neokyuubi
Copy link

neokyuubi commented May 17, 2019

I hope this can be merged soon, thank you so much for you continuing to work on this one.
For now i'm doing it like i wrote in here : #5076 (comment)

@acolchagoff
Copy link
Contributor Author

@kevin-brown none really, I only did it to satisfy @alexweissman (several comments above)

@acolchagoff
Copy link
Contributor Author

Anything I can do to help this along?

@acolchagoff
Copy link
Contributor Author

@kevin-brown I've updated this with the latest.

@acolchagoff
Copy link
Contributor Author

@kevin-brown can you give me a status update as to what your plan is here?

@stale
Copy link

stale bot commented Feb 8, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status: stale label Feb 8, 2020
@stale stale bot closed this Feb 15, 2020
@acolchagoff
Copy link
Contributor Author

stalebot...

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.

4 participants