Skip to content
This repository has been archived by the owner on May 18, 2018. It is now read-only.

Handling and validation of metadata in the requests? #64

Open
kwilczynski opened this issue Apr 12, 2018 · 0 comments
Open

Handling and validation of metadata in the requests? #64

kwilczynski opened this issue Apr 12, 2018 · 0 comments
Labels
enhancement New feature or request

Comments

@kwilczynski
Copy link
Contributor

Related to TritonDataCenter/triton-go#151.

We need to make sure that we can handle and validate the following scenarios when handling metadata:

  • No matadata (not added at all)
  • No metadata (as null)
  • Empty object (not as null)
  • Nested objects (another key-value pair/object inside)

We are assuming that metadata almost always is flat key-value map, but that might not always be the case (see the linked issue above) - and we won't be able to correctly parse JSON with a nested object into a type (struct) on the Go side, which could result in a panic being thrown.

@kwilczynski kwilczynski added the enhancement New feature or request label Apr 20, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant