Skip to content

Conversation

PieterjanDeClippel
Copy link

@PieterjanDeClippel PieterjanDeClippel commented Aug 26, 2025

PR Checklist

Please check to confirm your PR fulfills the following requirements:

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?

Generating component => specfile has component in declarations array instead of imports

See SO question

Linked isssues

What is the new behavior?

  • false => declarations
  • true or undefined => imports

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

@PieterjanDeClippel PieterjanDeClippel changed the title Spec standalone check (defaults to true now) fix(testing): Spec standalone check (defaults to true now) (#31035) Aug 26, 2025
@PieterjanDeClippel PieterjanDeClippel changed the title fix(testing): Spec standalone check (defaults to true now) (#31035) fix(@schematics/angular): Spec standalone check (defaults to true now) (#31035) Aug 26, 2025
@alan-agius4
Copy link
Collaborator

Please see: #31035 (comment)

@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 26, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Template for standalone-component-spec is wrong

2 participants