hashicorp / hashicorp/web-unified-docs

[Documentation] Talk about `null` on Type Constraints pages

Open
#770 1 comment 0 reactions 0 assignees View on GitHub
documentation Terraform CE
Dominant language
MDX
Stars
87
Forks
275
Avg merge
3d 18h
Merged PRs (30d)
199

Description

### Terraform Version

```shell
1.2.9
```

### Use Cases

Anyone trying to understand type constraints and `null`

### Attempted Solutions

Reading existing docs, they do not mention `null` being a valid value for all type constraint keywords/constructors

### Proposal

Add something to the following links to indicate that `null` is a valid passed in or default value for any type constraint.

- https://www.terraform.io/language/values/variables#type-constraints
- https://www.terraform.io/language/expressions/type-constraints
- https://www.terraform.io/language/expressions/types#types

cc @laurapacilio

### References

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reading the three linked Type Constraints and Types documentation pages, then compare how they currently describe valid values and defaults. Done means each relevant page clearly states that null is valid for any type constraint, with the documentation links remaining consistent.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.