{"action":"opened","issue":{"url":"https://api.github.com/repos/TrackableEntities/trackable-entities/issues/145","repository_url":"https://api.github.com/repos/TrackableEntities/trackable-entities","labels_url":"https://api.github.com/repos/TrackableEntities/trackable-entities/issues/145/labels{/name}","comments_url":"https://api.github.com/repos/TrackableEntities/trackable-entities/issues/145/comments","events_url":"https://api.github.com/repos/TrackableEntities/trackable-entities/issues/145/events","html_url":"https://github.com/TrackableEntities/trackable-entities/issues/145","id":174506968,"number":145,"title":"Removing and adding entity should restore to its original state","user":{"login":"tonysneed","id":2836367,"avatar_url":"https://avatars.githubusercontent.com/u/2836367?v=3","gravatar_id":"","url":"https://api.github.com/users/tonysneed","html_url":"https://github.com/tonysneed","followers_url":"https://api.github.com/users/tonysneed/followers","following_url":"https://api.github.com/users/tonysneed/following{/other_user}","gists_url":"https://api.github.com/users/tonysneed/gists{/gist_id}","starred_url":"https://api.github.com/users/tonysneed/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tonysneed/subscriptions","organizations_url":"https://api.github.com/users/tonysneed/orgs","repos_url":"https://api.github.com/users/tonysneed/repos","events_url":"https://api.github.com/users/tonysneed/events{/privacy}","received_events_url":"https://api.github.com/users/tonysneed/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/TrackableEntities/trackable-entities/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-09-01T12:08:49Z","updated_at":"2016-09-01T12:08:49Z","closed_at":null,"body":"This issue is related to PR #144: Failing Test: Removing and adding entity should not mark it as Added or Removed.\r\n\r\nWe currently don't support multi-action scenarios like this.  While we do support simple state transitions, it would require a whole other level of state management to handle scenarios where we need to know the prior state in order to set the current state when adding or removing entities.\r\n\r\nIn these cases, it is best for the user of the change tracker to set entity state to what is should be.  This can be done manually: `entity.TrackingState = TrackingState.Unchanged` (or Modified, etc).\r\n\r\nI'm willing to entertain a proposed implementation of multi-state transitions, but it could require substantial effort and a great deal of testing."}}
{"actor":{"display_login":"tonysneed"}}