Skip to content

/update endpoints should ignore events already marked clean #1

Description

@agforeman

There should be some check to see if a cleaning has already occurred. If so it should not be wiped from the database and recreated. Fixing this issue will require some design choices about how to properly update the cleanings collection. For example, if we don't drop these cleanings from the database and a new stay is scheduled in the period of time that the cleaning is scheduled we would need to break this cleaning up in to two cleanings and mark them appropriately.

Activity

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

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions