Releases · Frannsoft/FrannHammer

26 Nov 12:45

v0.7.2

7a8b286

Young Link, Ice Climbers and Terry added Latest

Latest

Merge pull request #300 from Frannsoft/young-link

young link now supported in Ultimate

Assets 2

13 Sep 11:59

Frannsoft

v0.7.1

1ba4aa5

Bug Fixes and new characters support

#294
#295

Assets 2

08 Aug 23:05

Frannsoft

v0.7.0

f978ccf

v0.7.0

Detailed changes for this release can be found here

The KH api is available at a new endpoint!

https://api.kuroganehammer.com

The previous endpoints have been retired and turned off. More information can be found here - https://github.com/Frannsoft/FrannHammer/wiki/v0.7.0-Update

Short version:

Ultimate data from @Kuroganehammer's site is now present - #262
Can query data by game with the new game query parameter - #259
Removed some unused endpoints - #258
Check out the new Related property on API responses - #265
Ultimate data shown in tooltips is partially available with the new expand query parameter #261

Minor changes:

Missing Smash4 Character Attribute data added - #248
Ness missing Run Speed on Smash4 Character Attributes - #256
PAC-MAN's grabs header listed on Moves - #257

Technical changes:

The API was migrated from ASP.NET Full Framework to ASP.NET Core - #260
KH site data is now stored entirely in memory instead of in an external store - #263

Assets 2

07 Feb 19:24

Frannsoft

v0.6.0

619edd8

v0.6.0 - 6/1/18

FrannHammer API version 0.6.0+ - Major Changes - 6/1/18

This documentation has been ported from a previous wiki page

Test out the current version here!

TL;DR

Can now get unique properties of a character back (e.g., Cloud's frame data with Limit)
Support for unique properties includes ability to scrape data outside of KuroganeHammer.com via Pull Requests
Now using MongoDb instead of Sql Server as a datastore
Custom response objects via fields in request url are deprecated
Responses now contain Hypermedia links
Hosted on Azure

Full project details here if you're interested - https://github.com/Frannsoft/FrannHammer/projects/1

It's been long time coming, but v0.6.0 is finally here. There are a ton of structural changes as well a slew of new features in this release. The tech stack and infrastructure has changed as well. This release has involved learning several technologies I've wanted to check out for a while and the problems I wanted to address in the API coincided with learning them.

It will still be a bit of time before this is merged into master since the changes are large.

Unique Character Properties:

Up until this release, the API had no ability to accommodate the unique properties of characters since they are all non-standard formats when compared with the rest of the moves and attributes for characters. An example of this would be Cloud's Limit Break info (Table labeled 'Limit Break' on Cloud's KH page).

The API can now handle storing this data. Right now, only Cloud's Limit Break data is stored, but I'll be adding in more of these tables as time goes on.

This also means data outside of KuroganeHammer.com can be stored and retrieved via the API. Pull Requests are welcome!

For an example of what this entails take a look at LimitBreakScraper and IUniqueDataScraper (C#). I'll follow up shortly with another post explaining this process in more detail. Feel free to ping me on twitter (@ FrannDotExe) or email me (address in my profile) in you have questions.

Current live Deployment:

http://beta-api-kuroganehammer.azurewebsites.net/api

Yes, that name is hideously long and annoying. It is also free!

I'm currently trying out Azure and if all goes well I will most likely move the production build to Azure as well. I get a lot more analytics and can respond to feedback much more quickly using Azure over the current host. Along with that, the current server has had a few issues crop up randomly that cause the API to malfunction (e.g., unplanned restarts with Sql Server not starting post-reboot).

Also, the database is now hosted by mLab. I've switched from Sql Server and Entity Framework to MongoDb with the C# driver. Storing data as documents rather than in tables of relational data increase flexibility a ton and was a major factor in enabling support for unique properties on characters.

The README file will be updated with info pointing to the beta deployment as well as keeping the existing master deployment people will use most often.

Hypermedia Support:

You'll notice a new property in response objects named Links. This contains endpoints for additional information around the resource you requested, hopefully making it easier to 'discover' other features as well as maintain them in your app. For more information on hypermedia APIs and HATEOAS take a look here.

Here's an example: http://beta-api-kuroganehammer.azurewebsites.net/api/characters/name/greninja (note: You might need to prettify this to make it a bit more readable)

Assets 2