Block gems that are yanked from being queried through the API #406

Closed
qrush opened this Issue Mar 7, 2012 · 4 comments

Projects

None yet

4 participants

@qrush
Member
qrush commented Mar 7, 2012

versions#show is a big one, I'm sure there's a few holes here.

@smoak
Contributor
smoak commented Apr 23, 2012

What would this entail? Just returning 404 if the gem is yanked?

@qrush
Member
qrush commented Apr 24, 2012

Yep! That should be enough... Make sure to check all of the endpoints :)

Sent from my iPhone

On Apr 23, 2012, at 6:40 PM, Scott Moak
reply@reply.github.com
wrote:

What would this entail? Just returning 404 if the gem is yanked?


Reply to this email directly or view it on GitHub:
#406 (comment)

@adkron
Contributor
adkron commented Nov 4, 2012

This should be closed. The code is already merged.

@cmeiklejohn
Contributor

🍻 🍺 🍻

@cmeiklejohn cmeiklejohn closed this Nov 4, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment