Skip to content

Added path '/api/public/find?q=<query>' to find cads via API with the same query syntax used in cards listing#413

Open
fafranco82 wants to merge 1 commit intoKamalisk:arkhamfrom
fafranco82:api-find
Open

Added path '/api/public/find?q=<query>' to find cads via API with the same query syntax used in cards listing#413
fafranco82 wants to merge 1 commit intoKamalisk:arkhamfrom
fafranco82:api-find

Conversation

@fafranco82
Copy link
Copy Markdown
Contributor

As I did in SWDestinyDB, this addition will be very helpful for 3rd party API consumers.

@IdleMuse
Copy link
Copy Markdown

I'd love this! Was doing some API stuff today and was amazed to see this doesn't exist.

@Entrox-Licher
Copy link
Copy Markdown

I'd like to bump this PR again; this is a feature I'd absolutely love, it would make referencing the API infinitely easier and more flexible, opening up a lot of new use cases.

@Kamalisk
Copy link
Copy Markdown
Owner

I am not totally opposed to the idea, but the intention of the api is for all the card data to be requested once, and cached or loaded into memory, and then use whatever your application is written in to query it. (the deck builder essentially does that, and makes all card look ups client side in js)

The main concern is the extra load on the server if applications start looking up every card instead of loading the data from local storage.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants