[#1895] Make postcode field non-nullable #874
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
pi-sigma
force-pushed
the
fix/1895-profile-page-null-values
branch
from
356e5ad
to
f2503d7
Compare
pi-sigma
force-pushed
the
fix/1895-profile-page-null-values
branch
from
f2503d7
to
b1a297d
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## develop #874 +/- ##
========================================
Coverage 92.79% 92.80%
========================================
Files 800 801 +1
Lines 27482 27500 +18
========================================
+ Hits 25503 25522 +19
+ Misses 1979 1978 -1 ☔ View full report in Codecov by Sentry. |
stevenbal
approved these changes
Dec 4, 2023
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.
Prevent
Nonefor postcode in profile templates by making postcode field non-nullableTaiga #1895