Repository navigation
fix(@schematics/angular): include the type separator in the class spec import - #34486
Merged
Merged
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the Angular class schematic template for spec files to correctly format the import path when a type option is provided, ensuring a dot is prepended to the type name (e.g., './foo.model' instead of './foomodel'). It also adds a corresponding unit test to verify this behavior. There are no review comments to address.
alan-agius4
added
target: patch
…c import
class spec template imports `'./<name><type>'`, and `type` reaches it without leading dot since class schematic moved to `generateFromFiles`
so `ng g class user --type=model` writes `user.model.spec.ts` with `import { User } from './usermodel'` and generated spec does not compile
template now adds dot only when type is set, matching `__type__` file name token
alan-agius4
force-pushed
the
class-spec-type-separator
branch
from
October 27, 2026 15:38
9d05cef to
718cb5f
Compare
Collaborator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Checklist
PR Type
What is the current behavior?
Issue Number: N/A
ng g class user --type=modelwritesuser.model.spec.tswithimport { User } from './usermodel', so generated spec fails with TS2307 (checked on 22.2.3)Since 322f6ec class schematic no longer prefixes
typewith dot, dot lives only in file name__name@dasherize__.__type__.spec.ts, while spec template still imports'./<%= dasherize(name) %><%= type %>'skipTestsis false by dafault and every class generated with--typegets this specWhat is the new behavior?
Template adds dot only when type is set, so import becomes
'./user.model'and without--typeit stays'./user'New case in
class/index_spec.tsfails on mainDoes this PR introduce a breaking change?
Other information
Raw
typeon purpose: class file name token is__type__without@dasherize, so import has to match itService and directive templates dasherize both sides