feat(docs-infra): added an existing content #56951
Closed
Conversation
This file contains 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
When migrating to adev, from 17.3.x, added an existing file, in the structure guide Fixesangular#56893
angular-robot
bot
added
detected: feature
|
We discussed it internally, it was a conscious choice to not migrate this file as it is not angular centric. That being said we acknoledge that a entry page to with several links, and basic infos on angular specific would be welcome. |
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.
When migrating to adev,from 17.3.x,this guide(typescript-configuration.md) was present in the structure, but after 17.3.x was removed, this PR adds to an existing file in the structure directory.
Fixes#56893
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number:#56893
What is the new behavior?
Does this PR introduce a breaking change?
Other information