KhronosGroup / KhronosGroup/Vulkan-Docs
`VkPresentScalingFlagBitsEXT` should have named `0`
Open
Nobody has claimed this yet.
System Integration
- Dominant language
- JavaScript
- Stars
- 3.3k
- Forks
- 549
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 2
Description
0 in VkPresentScalingFlagBitsEXT is a meaningful value, so it should have a named 0 value. Perhaps VK_PRESENT_SCALING_NOT_SUPPORTED_EXT = 0.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Vulkan specification entry for VkPresentScalingFlagBitsEXT and review how its zero value is represented. Add a name for the meaningful zero value as proposed in the issue, then check the surrounding enum documentation for consistent wording and formatting.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100