Skip to content
This repository has been archived by the owner on Apr 16, 2023. It is now read-only.

Support Nullable<> for indicating optional primitives #5

Open
2 of 4 tasks
teneko opened this issue Nov 4, 2022 · 0 comments
Open
2 of 4 tasks

Support Nullable<> for indicating optional primitives #5

teneko opened this issue Nov 4, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@teneko
Copy link
Member

teneko commented Nov 4, 2022

Currently you cannot use int? or other Nullable<>-wrappable primitives inside a schema. So you cannot use int? to indicate a block attribute or object attribute as optional.

Here are some facts that must be taken into account:

  • ITerraform<> can contain Nullable<>, but Nullable<> never ITerraform<>
  • Nullable<> can contain primitives and BigInteger
  • We have a to decode/encode ITerraform<Nullable<>> properly
@teneko teneko added the enhancement New feature or request label Nov 4, 2022
@teneko teneko added this to the v0.1.0 milestone Nov 4, 2022
@teneko teneko self-assigned this Nov 4, 2022
@teneko teneko changed the title Support Nullable<> for indicating optional primitives Support Nullable<> for indicating optional primitives Nov 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant