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.

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

Handle nullable output values marked as non-nullable in the schema #402

Open
myhau opened this issue Nov 8, 2023 · 1 comment
Open

Handle nullable output values marked as non-nullable in the schema #402

myhau opened this issue Nov 8, 2023 · 1 comment
Assignees

Comments

@myhau
Copy link
Member

myhau commented Nov 8, 2023

Ideas:

  • laziness (like in Besom)
  • default values (e.g. for String map it to "")
  • print error message with issue description and repository to raise it in
@jplewa
Copy link
Member

jplewa commented Apr 23, 2024

I reported this type of an issue in GCP ages ago and nothing so far: pulumi/pulumi-gcp#1125

jplewa added a commit that referenced this issue May 27, 2024
## Task

Related to: #402

## Description

This is absolutely not a fix, however no one will have the time to
actually fix this any time soon and right now there is no way to use
functions such as this one (we immediately get a NPE in `toKotlin`).
It's actually a great fear of mine that one of the libraries that I use
in my demo presentations will break like this 🙈 The actual fix will
presumably be to make all fields lazy and only report errors once
they're touched by the user. With this workaround we will at least have
a way to make a function/resource work after someone reports such a
problem in one of the providers.

---------

Signed-off-by: Julia Plewa <jplewa@virtuslab.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants