1. 20 Jun, 2020 1 commit
    • Kyle Clarke's avatar
      Split the payload generation into a separate callable method · 8b18758b
      Kyle Clarke authored
      Rather than have a json payload generated within the write json method,
      a caller may prefer to get the []bytes from the marshalled json to use
      instead. Separate method for callers so that bytes can be written to
      different writers as required.
  2. 03 Jun, 2020 1 commit
  3. 24 May, 2020 2 commits
    • Kyle Clarke's avatar
    • Kyle Clarke's avatar
      Removal of the SetSingle method vs Set and Add · 33f80435
      Kyle Clarke authored
      The data returned in the response can be that either of an array
      collection or a single object. The difference is now implied based on
      the caller. Eg Add() will deem that the entry to be added to a
      collection, where Set will deem the response data is an object, not a
      collection. Multiple sets will overwrite previously set data.
      Note you can still access the public property of AsCollection on
      Response object should you want to alter default behaviours.
  4. 22 May, 2020 2 commits
  5. 25 Mar, 2018 2 commits
    • Kyle Clarke's avatar
    • Kyle Clarke's avatar
      Error payload not rendered, test failures · 2d51e184
      Kyle Clarke authored
      When running the package tests, an error was raised with the marshal of
      an error payload. This is odd to me as this test passed in past. But
      looking at the code, the anonymous struct used to render an error
      payload did not have a public field associated, so I can understand why
      the error payload was empty.
      What is unclear to me however, is that the private meta and link fields
      DO still render without a public field set on the anonymous struct. The
      difference being that the meta and link fields are pointers. I don't
      understand the difference yet as to why that works. I will confirm.
      Regardless, I am no explicit on public field values on the anonymous
      struct as it should be.
  6. 01 Mar, 2018 1 commit
  7. 05 Jul, 2017 1 commit
  8. 04 Jul, 2017 2 commits
  9. 01 Jul, 2017 3 commits
  10. 23 Jun, 2017 1 commit
  11. 30 Dec, 2016 15 commits
  12. 29 Dec, 2016 2 commits
  13. 28 Dec, 2016 1 commit
  14. 25 Dec, 2016 1 commit
  15. 24 Dec, 2016 4 commits
  16. 22 Dec, 2016 1 commit