OWASP/Nest

Removing `undefined` type or `?` specifier.

Open

#4,833 opened on Jun 4, 2026

View on GitHubContributor guide
 (4 comments) (0 reactions) (0 assignees)Python (651 forks)auto 404
good first issue

Repository metrics

Stars
 (412 stars)
PR merge metrics
 (Avg merge 2d 12h) (128 merged PRs in 30d)

Description

Description

SonarCloud reports a violation of rule typescript:S4782. Optional property declarations should not use both ? and undefined.

Sonar Issue

https://sonarcloud.io/project/issues?open=AZ5vYOWvEtPFZsxg7_Xu&id=OWASP_Nest

Affected Code

excludedUsernames?: Array<string> | string | null | undefined;

Note

In many file same SonarCloud violation Consider removing 'undefined' type or '?' specifier, one of them is redundant.

Contributor guide

Research direction
Review the SonarCloud rule typescript:S4782 to understand the redundancy. Search the codebase for optional properties using both '?' and 'undefined', e.g., 'excludedUsernames?: Array<string> | string | null | undefined'. Decide whether to keep '?' and remove 'undefined' or remove '?' and keep 'undefined' based on the code logic. Apply changes consistently, then run the TypeScript compiler and tests to ensure no behavior changes.
Tech stack
typescript
Domain
frontend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80