fix(@schematics/angular): use proper variable in resolver functional spec

[cexbrayat]

PR Checklist

Please check to confirm your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular-cli/blob/main/CONTRIBUTING.md#-commit-message-guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

The current functional resolver generates:

const executeResolver: ResolveFn<boolean> = ...

it('should be created', () => {
  expect(resolver).toBeTruthy();
});

with resolver a variable that is never declared

What is the new behavior?

const executeResolver: ResolveFn<boolean> = ...

it('should be created', () => {
  expect(executeResolver).toBeTruthy();
});

Does this PR introduce a breaking change?

• Yes
• No

Other information

[alan-agius4]

Thanks for this.

@cexbrayat can you also please send a fix for

angular-cli/packages/schematics/angular/guard/type-files/__name@dasherize__.guard.spec.ts.template

Line 16 in ae85cce

expect(<%= camelize(name) %>Guard).toBeTruthy();

?

[cexbrayat]

@alan-agius4 Haha, yes, I was on it #24333

[alan-agius4]

@alan-agius4 Haha, yes, I was on it #24333

Thanks for next time, it would be better to do a single PR with different commits instead of opening 3 different PRs.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}