Skip to content

fix: getProposal api error - #1613

Closed
ellen-wright wants to merge 2 commits into
developfrom
1620-fix-getProposal-api-error
Closed

fix: getProposal api error#1613
ellen-wright wants to merge 2 commits into
developfrom
1620-fix-getProposal-api-error

Conversation

@ellen-wright

@ellen-wright ellen-wright commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

Description

refs: UserOfficeProject/issue-tracker#1620
There has been an error when calling the getProposal api call that the isComplete cannot be null.
This can be resolved by allowing it to be null.

This includes schema changes that need to be approved

Tests included/Docs Updated?

  • I have added tests to cover my changes.
  • All relevant doc has been updated

@ellen-wright
ellen-wright requested a review from a team as a code owner June 30, 2026 08:40
@ellen-wright
ellen-wright requested review from EdwardHaynes and removed request for a team June 30, 2026 08:40
@ellen-wright ellen-wright changed the title fix getProposal api error fix: getProposal api error Jun 30, 2026
@ellen-wright
ellen-wright requested review from deepaksftc and jekabs-karklins and removed request for EdwardHaynes June 30, 2026 08:40
@ellen-wright ellen-wright added the breaking:change A change that could disrupt external dependencies label Jun 30, 2026
@zacharyjhankin

zacharyjhankin commented Jun 30, 2026

Copy link
Copy Markdown
Collaborator

I don't understand the purpose of this PR. This API ultimately calls QuestionaryDataSource.ts (getIsCompleted) which returns a promise(boolean) So why do we need to allow the API to return null if it can't return null given its implementation? What is the issue you are facing?

@jekabs-karklins

Copy link
Copy Markdown
Contributor

I also believe that the problem is somewhere else. By inspecting code I can see that if it is undefined or null in the datasource it should be set to false upstream

I think we would want to investigate to see how does isComplete become null and fix it there, maybe?

@ellen-wright

Copy link
Copy Markdown
Contributor Author

Thanks for the help, I will close this PR and do some more looking into it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

breaking:change A change that could disrupt external dependencies

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants