1.0.0b3

Changes

• BaseContext.respond now has slightly different semantics:
  • Passing a value of None as an argument leads to that parameter not being sent to the API. This has always been the case for all parameters except content, which used to cast the None to a string.
  • Passing a falsy value that is not None (e.g. embeds=[]) now sends the empty value to the API. You are responsible for making sure that at least one value is not empty (client-side validation only ensures one is passed).

Fixes

• Calls of the form BaseContext.respond(embed=...) (i.e. only embed is passed) work again now.
• Multiple responses to the same interaction now actually edits the response again.