Skip to content

Generic properties created and modified for all resources #75

Open
Open
Generic properties created and modified for all resources#75

Description

@kba
kba
opened on Nov 30, 2015

All resources, regardless of their semantics, should have created/modified properties, which should be set, resp. for every POST/PUT request.

This is important for paging (c.f. #74).

Need to decide on good names for those

  • created and modified
    • PRO: Easy to remember
    • CON: Can interfere with semantics
  • _created and modified
    • PRO: Clear because underscore-prefixed names are private by convention
    • CON: Might interfere with other Monoose plugins or MongoDB conventions (need to investigate)
  • _mongoosejsonld_created and _mongoosejsonld_created
    • PRO: No conflicts possible
    • CON: Long and ugly

I'm also open for suggestions @infolis/developers

Activity

  1. bolandka commented on Dec 2, 2015

    @bolandka
    bolandka
    on Dec 2, 2015
    Member

    I would tend to not using created and modified, indeed this might be confusing. When using the long and ugly variant it should be clear that, in the case of InfolisFiles for example, this refers to the creation / modification of the InfolisFile resource rather than the creation / modification of the underlying document.

    How about calling it resource_created and resource_modified?

  2. kba commented on Jun 14, 2016

    @kba
    kba
    on Jun 14, 2016
    ContributorAuthor

    This is now live (resource_created and resource_modified). Still open how/if we expose this as LD.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions