danivek/json-api-serializer

Issues

• Support for relationship data serialization?

  #97 opened 5 years ago by ckeboss
  2

• Having no attributes in the relation data does not add relation to included array

  #134 opened 3 years ago by AmauryD
  0

• bug: `id` is set to exclude attribute in deserialization and still included as `undefined`

  #69 opened 6 years ago by diosney
  12

• Error thrown when relationship is not registered

  #129 opened 3 years ago by Istanful
  5

• The result after serialize will not have `included` if the input doesn't have attributes

  #128 opened 3 years ago by yidongw
  5

• Is there an option to remove undefined properties?

  #127 opened 3 years ago by yidongw
  1

• Unintended object in attributes

  #122 opened 4 years ago by shankiflang
  2

• Would you be interested in a conversion to Typescript?

  #109 opened 4 years ago by kristof-mattei
  2

• TypeScript Definitions

  #60 opened 6 years ago by johannesschobel
  11

• Case conversion breaks on non-alphanumeric strings

  #118 opened 4 years ago by alexzherdev
  0

• Incorrectly deserializing relationship when alternativeKey is set from default and relationship data is not in the included array

  #116 opened 4 years ago by itskingori
  2

• ValidationError: beforeSerialize is not allowed

  #114 opened 4 years ago by nrcmkoh
  2

• Always return "included" where "include" has been requested (v1.1)

  #35 opened 7 years ago by noetix
  11

• Error instance serialization missing properties

  #110 opened 4 years ago by john-goldsmith
  1

• Client side deserialization

  #64 opened 4 years ago by asalisaf
  2

• ErrorMaximum call stack size exceeded if `included` has cross references

  #106 opened 5 years ago by max-konin
  0

• Any way to support computed attributes?

  #66 opened 5 years ago by saygun
  5

• id not defined by a single column

  #37 opened 5 years ago by chamini2
  10

• Error when try to deserialise an included relationship with `alternativeKey`

  #103 opened 5 years ago by max-konin
  3

• ObjectID (mongodb) should be serialized with .toString() and not treated as an object

  #100 opened 5 years ago by c-dima
  2

• Support extracting error class names into the 'title' field of JSON API errors

  #102 opened 5 years ago by calmcl1
  1

• bug: Duplicated models from includes are removed from response

  #89 opened 5 years ago by EspadaV8
  1

• Support serialization of only meta

  #91 opened 5 years ago by ckeboss
  2

• Use a cache for converting to snake/camel/kebab case

  #84 opened 5 years ago by alechirsch
  1

• Relationships do not work with ES2015 classes

  #88 opened 5 years ago by firechicago
  0

• bug: When installed in Angular project, it throws error since it is searching for `fs`

  #87 opened 5 years ago by diosney
  3

• Empty relationships returned as data: null.

  #41 opened 5 years ago by wesselvdv
  11

• Serializing JS Date objects returns empty objects

  #83 opened 5 years ago by alechirsch
  1

• Deserializing included relationships will not check for registered type

  #81 opened 5 years ago by igneel64
  0

• convertCase converts arrays to objects

  #80 opened 5 years ago by stefanvanherwijnen
  0

• Null as data in _convertCase throws an error

  #77 opened 5 years ago by stefanvanherwijnen
  1

• Is it possible to include resource level meta information?

  #73 opened 5 years ago by kbsanders
  2

• Replace Joi with AJV

  #63 opened 5 years ago by faustbrian
  4

• Id always serialized as string

  #72 opened 5 years ago by Hardsix
  2

• Deserializing relationships to an object

  #65 opened 6 years ago by stefanvanherwijnen
  13

• Should be able to return "Resource Identifier Objects"

  #62 opened 6 years ago by dimisus
  4

• deserializeResource fails when blacklistOnDeserialize is set but no attributes are present

  #61 opened 6 years ago by pichfl
  0

• Error handling is missing in the documentation

  #56 opened 6 years ago by jex310
  2

• Nested Schema

  #58 opened 6 years ago by Kinetic-Pulse
  11

• dynamic type

  #54 opened 7 years ago by jamesdixon
  11

• behavior when data is null or empty

  #53 opened 7 years ago by jamesdixon
  5

• jsonapiObject: false throwing error

  #52 opened 7 years ago by jamesdixon
  3

• Deserialize async?

  #46 opened 7 years ago by officer-rosmarino
  3

• Acceptance of malformed relationships

  #49 opened 7 years ago by chamini2
  2

• Error deserializing null relationships

  #45 opened 7 years ago by chamini2
  3

• Dinamically avoid certain fields in certain JSON-API response

  #47 opened 7 years ago by officer-rosmarino
  4

• Suggestion: Allow alternativeKey to be a path

  #43 opened 7 years ago by russellhill
  0

• Missing dependency

  #42 opened 7 years ago by danherd
  1

• Empty relationships should have data key with value null

  #38 opened 7 years ago by JakeDluhy
  3

• Duplicate type + id in included, but different data.

  #39 opened 7 years ago by wesselvdv
  7