Skip to content

Conversation

@idlewis
Copy link
Member

@idlewis idlewis commented Apr 13, 2016

Only published assets are hidden, so instead of making the hidden asset
match the state of the previous asset, it is safe to explicitly make it
published. This avoids an edge case where

  • a previous 'hide' has failed, leaving an unpublished matching asset
  • on retry, the AddThenDeleteStrategy matches the state of the new
    'hidden' asset to the unpublished state of the failed 'hidden' asset,
    instead of matching the published state of the old, visible asset

Only published assets are hidden, so instead of making the hidden asset
match the state of the previous asset, it is safe to explicitly make it
published. This avoids an edge case where
 - a previous 'hide' has failed, leaving an unpublished matching asset
 - on retry, the AddThenDeleteStrategy matches the state of the new
'hidden' asset to the unpublished state of the failed 'hidden' asset,
instead of matching the published state of the old, visible asset
@Azquelt Azquelt merged commit 5179886 into WASdev:master Apr 14, 2016
@idlewis idlewis deleted the always_publish branch April 14, 2016 10:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants