abpframework / abpframework/abp
DTOs in @abp/ng.core are not suitable for strict null checks
Open
Nobody has claimed this yet.
priority:normal
problem
ui-angular
- Dominant language
- C#
- Stars
- 14.4k
- Forks
- 3.7k
- Avg merge
- 15h 32m
- Merged PRs (30d)
- 106
Description
Example: EntityDto has an optional id, but it is not (and cannot be) optional.
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 EntityDto and the other DTO declarations in @abp/ng.core, then inspect how they behave with TypeScript strict null checks. Identify the intended required and optional fields from the existing types and usage; done means the DTO declarations accurately represent those constraints and compile under strict null checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100