René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add model flags to control which crud method should be executed on sync","articleBody":"### Environment\r\n* DiffSync version:  1.3.0\r\n\r\n### Proposed Functionality\r\nIt would be very useful to have a few more Model flags to control which CRUD methods (create/update/delete) would be called during a sync()\r\n\r\nI would like to propose \r\n- `CRUD_NO_UPDATE`: Do not call update() on the DiffSyncModel during sync(), the model and the changes will still be visible in the diff.\r\n- `CRUD_NO_DELETE`: Do not call delete() on the DiffSyncModel during sync(), the model and the changes will still be visible in the diff.\r\n- `CRUD_NO_UPDATE_DELETE` = `CRUD_NO_UPDATE` | `CRUD_NO_DELETE`\r\n\r\nI wish we could support CRUD_NO_CREATE but I don't think this is possible right now because we can't pass context to this method since the model doesn't exist yet.\r\n\r\n### Use Case\r\nThe main use case for me would be to `protect` some object to be `READ_ONLY` but still show up in the diff while other objects of the same type would remain `READ_WRITE`.\r\nAs an example\r\nWhen using the network-importer, once we have done the initial import of the SOT and the data has been cleaned up, it would be useful to `protect` some objects from being updated/deleted in the SOT but it's still interesting to have these objects show up in the diff.\r\nToday for this use case we are using the flag `IGNORE` but the object is completely ignored and doesn't show up in the diff at all.\r\n\r\n","author":{"url":"https://github.com/dgarros","@type":"Person","name":"dgarros"},"datePublished":"2021-12-16T18:46:22.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/85/diffsync/issues/85"}