Add types for baton, flux, log.lua. Change rxi-json-lua to be more specific

[icy-lava]

Definitions for these libraries:

• https://github.com/tesselode/baton
• https://github.com/rxi/flux
• https://github.com/rxi/log.lua
• https://github.com/rxi/json.lua

I changed json.lua to use more specific types rather than any.
You can still force it to accept any value like so:

local json = require 'json'

local t: table = {value = 'data'}

local encoded = json.encode(t as json.Value)
local decoded = json.decode(encoded) as any

[hishamhm]

Cool, thanks!

My 2 cents on the json changes:

I think updating the json decode definition should be fine, since the one with any requires as casts to use it in any form anyway and this new one might allow more useful behavior with is on the result.

I think for encode, any should be fine though? After all, most likely this library will be taking other table types, and casting as json.Value does not provide anything in terms of checking/validation, so ultimately it's up for json.encode to validate the input. So keeping the encode signature as is with any would make it more convenient, IMO.

[icy-lava]

Yeah that's fair. Another option would be to make the encode more lenient:

encode: function(value: number | boolean | string | table): string

That way simple simple errors like directly passing in a function or cdata/userdata would be caught, but tables containing invalid types would still be only caught at runtime.

Since this is not a common scenario I'm ok with making the encode input any though.

Also, now that I think about it, you have the option to use compile time validation yourself:

local obj: json.Object = {value = 'data'}
local encoded = json.encode(obj)

[hishamhm]

The table type is a bit wonky (it's an alias to {any:any}) so I think just keeping encode using any should be okay for now.

Thank you for the revision!