template-no-call-expression: not reporting failures in specific cases
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 2.5k
- Forks
- 232
- PR merge metrics
- No merged PRs in 30d
Description
**Reproduction:**
```JSON
{
"rules": {
"template-no-call-expression": true
}
}
```
```ts
@Component({
template: `
{{ obj?.nested1() }}
{{ obj!.nested1() }}
`
})
class TestComponent {}
```
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 implementation and tests for the template-no-call-expression rule, then run the supplied Angular component reproduction. Check why optional chaining and non-null assertion calls produce no diagnostics; done means both expressions report failures under the shown configuration and regression coverage is added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100