I'm at least 90% sure this is possible because json2typescript does everything through runtime reflectino magic.

Deadline: March 31st

https://derpibooru.org/forums/meta/topics/old-api-deprecation-notice

Global request caching is still an important feature to add. I think it would be relatively easy to do, as most HTTP fetching is routed through Fetch anyway.

The question is, do I want this to be done in memory or on disk, or a combination of the two? Should it be user-configurable?

Tags can be fetched at both tags/NAME.json and tags/ID.json, where tags/NAME.json takes priority

So, if I named a tag 12345, whatever tag ID 12345 is would no longer be fetchable by ID.

Looks like I'll have to update my tag fetching stuff to fetch by name instead. Which also means I'll need byte[]'s sluggify code.

new_name.gsub!('-', '-dash-')
new_name.gsub!('/', '-fwslash-')
new_name.gsub!('\\', '-bwslash-')
new_name.gsub!(':', '-colon-')
new_name.gsub!('.', '-dot-')
new_name.gsub!('+', '-plus-')

Thanks, Derpi.

https://derpibooru.org/search/reverse.json

• multipart/form-data/application/json
• key - API key
• image - binary image data
  • or: scraper_url - url to image
    returns:

{
  "search": [
    {
      // image object
    }
  ],
  "total": 1
}

Seems like duplicate effort, since assignment of the default options also happens within fetchJSON

Possible options:

• json2typescript (most likely)
• serializer.ts
• json-typescript-mapper