Revert "feat: API changes for handling new submission_email location"
#3606
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
|
Removed vultr server and associated DNS entries |
Merged
RODO94
approved these changes
Sep 2, 2024
|
I worked on an additive fix for this regression failure, but I couldn't come up with one today. We will merge this to allow other work to move along and look to add a bug fix later |
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.
Reverts #3582 due to failing regression tests
✅ Regression test passing on this branch here - https://github.com/theopensystemslab/planx-new/actions/runs/10643974774
I suspect that this is due to the field
TeamSettings.submissionEmailstill being valid here - as it's not removed, there may be a reference to it somewhere that wasn't caught in #3582?