Repository navigation
docs(@schematics/angular): correct directory and entryFile option descriptions - #34364
Merged
Merged
Conversation
… descriptions The `ng new` `directory` option claimed the workspace is created in the current directory when the option is omitted, but a new directory named after the workspace is created instead. The library `entryFile` option described a path relative to the workspace root, but the value is a file name without the `.ts` extension that is placed in the library's `src` directory.
angular-robot
Bot
added
area: docs
![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 descriptions of schema properties in Angular schematics to clarify their behavior: entryFile in the library schema is now described as a file name without the .ts extension, and directory in the ng-new schema clarifies that a new directory is created if not specified. Feedback suggests removing the "format": "path" attribute from entryFile since it no longer represents a standard path, preventing potential issues with IDEs and GUI tools.
alan-agius4
requested changes
Oct 16, 2026
alan-agius4
added
the
action: cleanup
alan-agius4
added
target: patch
alan-agius4
added
action: merge
… option descriptions Co-authored-by: Alan Agius <alan.agius4@gmail.com>
… option descriptions Co-authored-by: Alan Agius <alan.agius4@gmail.com>
alan-agius4
force-pushed
the
docs/schematic-option-descriptions
branch
from
October 16, 2026 09:32
a4a19d1 to
8602c39
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
3 participants
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.
The
ng newdirectoryoption claimed the workspace is created in the current directory when the option is omitted, but a new directory named after the workspace is created instead. The libraryentryFileoption described a path relative to the workspace root, but the value is a file name without the.tsextension that is placed in the library'ssrcdirectory.