Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Resolve use of non-null assertions in types for GET #148

Open
kevin-pierce opened this issue Jul 14, 2023 · 0 comments
Open

Resolve use of non-null assertions in types for GET #148

kevin-pierce opened this issue Jul 14, 2023 · 0 comments
Assignees
@kevin-pierce

Comments

@kevin-pierce
Copy link
Contributor

kevin-pierce commented Jul 14, 2023 •
edited
Loading

The goal of this issue is to investigate the definition of our types and remove all non-null assertions currently being used as a work-around.
@kevin-pierce kevin-pierce self-assigned this Jul 14, 2023
@kevin-pierce kevin-pierce changed the title DRAFT: Resolve use of non-null assertions in types for GET Resolve use of non-null assertions in types for GET Jul 14, 2023
This was referenced Jul 14, 2023
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kevin-pierce kevin-pierce

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kevin-pierce