v1.1.1

• JSONRPC2.Servers.HTTP.Plug will now accept any content-type and attempt to parse it as json, but it also is Plug.Parsers friendly. This should resolve recent issues around content-type-related request failure. If you have a chain of plugs, (such as in a Phoenix Endpoint or Plug Builder/Router), you should note that Plug only allows the body to be retrieved once, so you must mount Plug.Parsers above JSONRPC2.Servers.HTTP.Plug. If you do not, the body will be consumed by JSONRPC2.Servers.HTTP.Plug and will be unavailable to plugs which are later in the chain.
• Examples have been formatted and added to the formatter config
• JSONRPC2.Clients.HTTP now uses the "content-type" header "application/json" by default, but this is easily overridden to be no explicit header (the previous default) or another content type
• JSONRPC2.Clients.TCP will no longer provide nil as a pid for "notify" casts to shackle, and instead uses a dead processes PID so that messages sent as a result of a notify are discarded
• JSONRPC2.Server.Handler updated to no longer use System.stacktrace/0 in a deprecated way
• Allow Poison ~> 4.0
• Require Plug ~> 1.3
• Add some more tests and clean up ignorable dialyzer errors in intentionally broken test code