Open RachelElysia opened 3 months ago
Thanks for tracking this @RachelElysia!
Users should know what fields can be undefined, or defined as null and why.
If I'm understanding correctly, the problem is that it's not clear what the best practice is for defining empty values for options in the PATCH /config
endpoint.
As an API user, when should I set an option to null
v. empty string v. undefined?
Rachel, which options could use this best practice?
Maybe we solve this w/ updates to the PATCH /config
docs.
FYI @rachaelshaw
Hey @RachelElysia, because we pulled this story into the current design sprint, I updated the issue description to user story format.
I moved your original issue description here for safekeeping:
Problem
- The frontend should work seamlessly with the API.
- Users should know what fields can be undefined, or defined as null and why.
- Users should know how to properly patch to /config
Potential solutions
- Address FE painpoints and determine if they are painpoints only in our frontend code, or if they are also found as painpoints in our API and documentation of our API.
- Which values can be undefined? Which values can be set to null? Which values can be set to 0? Which values will be undefined or null instead of an empty string?
@RachelElysia this didn't make it through the current design sprint, bringing back to Feature Fest
I think this story meets the definition of an engineering initiated story.
Removing ~feature-fest
and ~engineering-initiated
FYI @lukeheath and @RachelElysia
@RachelElysia Thanks for filing this! I'm prioritizing for estimation.
Chatting w/ @ddribeiro: Dale was building an iOS app on top of the Fleet API and not knowing which fields return null
, 0
, empty string was tough.
Getting this wrong would crash the app in some instances.
Probably a separate story but just leaving this here.
Goal
PATCH /config
endpoint in REST API docs,null
,0
, omit)PATCH /config
endpoint.Context
Changes
Product
Engineering
QA
Risk assessment
Manual testing steps
Testing notes
Confirmation