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

v0.11.2 #1193

Open
wants to merge 10 commits into
base: master
Choose a base branch
from
Open

v0.11.2 #1193

wants to merge 10 commits into from

Conversation

jharding
Copy link
Contributor

No description provided.

@jharding jharding added this to the 0.11.2 milestone Apr 27, 2015
@nostalgiaz
Copy link

👍 I need this patch

@nostalgiaz
Copy link

I don't need this anymore... I rolled back to the 0.10.5.

@tm1000
Copy link

tm1000 commented Jun 15, 2015

@AndrewCarterUK completely agree. It's baffling that there are over 33 valid pull requests and not a single action.

@Downchuck
Copy link

@jharding What's the status on this project? It seems temporarily abandoned.

@tm1000
Copy link

tm1000 commented Jul 9, 2015

@Downchuck There is a tweet from one of the lead developers that states they are only fixing issues in version 1.0 which, as you can see, is semi-vaporware. It would be nice if these simple things could be merged to tide us over though.

https://twitter.com/JakeHarding/status/598947982881390592

@Downchuck
Copy link

@tm1000 looks like they should have release 0.11 as 1.0, regardless of bugs, as it's an API change from 0.x.

@dougaxe1
Copy link

The fix in 173b4b5 appears to be a sufficient fix for the litany of issues and PRs around this issue. Any chance of this release getting fast tracked so we can close out #1212, #1224, #1284, #1316, #1319, #1331, and #1332 (among others)?

@ahmetabdi
Copy link

👍 Please fast track

@PikachuEXE
Copy link

It's been almost a year (just a few days left) since the last release
Is there a schedule for next release?

@tsamaya
Copy link

tsamaya commented Sep 14, 2016

Will it be merged into master once ?

@tm1000
Copy link

tm1000 commented Sep 14, 2016

This project is essentially dead and only twitter knows why.

@tm1000
Copy link

tm1000 commented Sep 14, 2016

Updated library in active development (a fork of this one from some great users)

https://github.com/corejavascript/typeahead.js

Copy link

@aranhaqg aranhaqg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need this patch

@and-semakin
Copy link

Legacy software is so legacy

@PikachuEXE
Copy link

I really wonder why this thing is not released for a whole year
Maybe no one is maintaining it?

@ahmetabdi
Copy link

I really wonder why this thing is not released for a whole year
Maybe no one is maintaining it?

That is exactly why!

@tsamaya
Copy link

tsamaya commented Jan 3, 2019

Personally and for my company we started to use
https://www.npmjs.com/package/jquery-typeahead

@CLAassistant
Copy link

CLAassistant commented Jul 18, 2019

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 4 committers have signed the CLA.

✅ charlotte-miller
❌ Jake Harding
❌ evverx
❌ jharding


Jake Harding seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

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

Successfully merging this pull request may close these issues.