Hacker News Reader

Hacker News

Comment by paulhallett | Hacker News Reader

Parent Full thread

paulhallett

As well as ID, we'll do some fuzzy matching on the URLs as well, so

GET /api/vehicle/t-65-x-wing

and

GET /api/planets/mustafar

will also work

View on HN

I think it would be nice to also provide an endpoint that lists all the resources as an array of objects where the key is the id and the value is the name. Maybe something like this:

  GET /resources/ships
  [
    { 1 : "Tantive IV" },
  ]

So RESTfully, I think this is normal. You should be able to call a resource and then be fed back all of those resources (usually paginated to say, 20 per request).

It will have this style of lookup.

Do you mind discussing how you did the fuzzy matching?

My initial guess would've been dynamic programming (levenstein distance), but if this is API-wide, did you make a suffix tree?

This doesn't work on pokeapi.co

PokeAPI is getting an update - http://phalt.co/if-you-have-data-they-will-consume-it/

and it will have better fuzzy matching.

Reply on news.ycombinator.com