-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LINK-1359 | Signup presence_status field #659
Conversation
eaef3cf
to
6a9a2f9
Compare
Codecov Report
@@ Coverage Diff @@
## main #659 +/- ##
==========================================
+ Coverage 76.10% 76.17% +0.06%
==========================================
Files 242 241 -1
Lines 17400 17392 -8
==========================================
+ Hits 13242 13248 +6
+ Misses 4158 4144 -14
... and 7 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
b25b375
to
aea117e
Compare
- In PUT request, validate existing date_of_birth or mandatory field value the those attributes are missing from the payload
…uest if value is missing from the payload
- In PUT request, validate existing date_of_birth or mandatory field value the those attributes are missing from the payload
…uest if value is missing from the payload
abf9ec2
to
4b33108
Compare
cefbf01
to
8464278
Compare
Kudos, SonarCloud Quality Gate passed! |
Description
Add presence_status field to Signup model. At the moment allowed values are
present
andnot_present
, but we might later add some other values e.g.partially_present
. That's the reason to use enum value instead of e.g. simple booleanis_present
fieldAlso allow mandatory_fields and
date_of_birth
field to undefined in the payload to update Signup. In that case use existing values for validationCloses
LINK-1359
Additional info
Link to FE PR: City-of-Helsinki/linkedcomponents-ui#206