Fix period progression update error #928
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
simenheg
force-pushed
the
fix-progress-update-error
branch
2 times, most recently
from
6558505 to
fc4fef1
Compare
petterhj
approved these changes
Nov 16, 2023
Don't attempt to update legacy period progression on objective updates anymore, as objectives are decoupled from their legacy periods automatically when they're updated now, making the update fail.
simenheg
force-pushed
the
fix-progress-update-error
branch
from
fc4fef1 to
0ba00bd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Don't attempt to update legacy period progression on objective updates anymore, as objectives are decoupled from their legacy periods automatically when they're updated now, making the update fail.