sequiturs/bookshelf-advanced-serialization

Issues

• Serializing relations fetched with collections

  #11 opened 7 years ago by JohnWestwig
  1

• Allow incomplete specification of context designations for a given table, with sane defaults

  #10 opened 7 years ago by ihinsdale
  0

• Support for create/update/destroy?

  #8 opened 7 years ago by jordansexton
  4

• `ensureRelationsLoaded` when used with a collection should yield 1 join, not n joins

  #9 opened 7 years ago by ihinsdale
  0

• Webpage down

  #7 opened 8 years ago by benjaminjs
  1

• Use consistent terminology

  #2 opened 8 years ago by ihinsdale
  0

• Consider serializing a clone that does not have unnecessary relations, rather than deleting relations from the original model

  #6 opened 8 years ago by ihinsdale
  0

• Support passing `accessor` option to Collection constructor

  #5 opened 8 years ago by ihinsdale
  0

• Warn if `shallow:true` and `ensureRelationsLoaded` options are both passed to `toJSON`

  #4 opened 8 years ago by ihinsdale
  0

• Only load relations that are in the final list of visible properties

  #1 opened 8 years ago by ihinsdale
  0

• Make handling of `contextSpecificVisibleFields` completely analogous to handling of `ensureRelationsLoaded`

  #3 opened 8 years ago by ihinsdale
  0