Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Angular 17 Tutorial : confusing sentence #54792

Closed
ByronMike opened this issue Mar 9, 2024 · 1 comment
Closed

Angular 17 Tutorial : confusing sentence #54792

ByronMike opened this issue Mar 9, 2024 · 1 comment
Labels
area: adev Angular.dev documentation good first issue An issue that is suitable for first-time contributors; often a documentation issue. help wanted An issue that is suitable for a community contributor (based on its complexity/scope). P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent state: has PR
Milestone

Comments

@ByronMike
Copy link

Describe the problem that you experienced

In the "essentials" section, there is a confusing sentence which affirms : " In this guide, we'll take a look at two primary categories of user interaction: event handling and forms."

Nevertheless, in this section the tutorial only discusses about event handling not forms.

After some research, I have found this tutorial about forms : "https://angular.dev/guide/forms" but when we arrive in the "Essentials" section, this form tutorial is not tackled.

Enter the URL of the topic with the problem

https://angular.dev/essentials/handling-user-interaction

Describe what you were looking for in the documentation

I was looking for a sub-section about forms or a link which redirects to the specific form tutorial.

Describe the actions that led you to experience the problem

Follow the "essentials" path to learn Angular.

Describe what you want to experience that would fix the problem

No response

Add a screenshot if that helps illustrate the problem

No response

If this problem caused an exception or error, please paste it here

No response

If the problem is browser-specific, please specify the device, OS, browser, and version

No response

Provide any additional information here in as much as detail as you can

No response

@JeanMeche JeanMeche added help wanted An issue that is suitable for a community contributor (based on its complexity/scope). good first issue An issue that is suitable for first-time contributors; often a documentation issue. area: adev Angular.dev documentation labels Mar 9, 2024
@ngbot ngbot bot added this to the needsTriage milestone Mar 9, 2024
Yash7824 added a commit to Yash7824/angular_github that referenced this issue Mar 10, 2024
@bencodezen bencodezen added the P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent label Mar 12, 2024
@ngbot ngbot bot modified the milestones: needsTriage, Backlog Mar 12, 2024
vladboisa added a commit to vladboisa/angular that referenced this issue Mar 17, 2024
Remove the confuse sentences with 2 categories, and rephrase

Fixes angular#54792
atscott pushed a commit that referenced this issue Mar 29, 2024
Remove the confuse sentences with 2 categories, and rephrase

Fixes #54792

PR Close #54914
ilirbeqirii pushed a commit to ilirbeqirii/angular that referenced this issue Apr 6, 2024
Remove the confuse sentences with 2 categories, and rephrase

Fixes angular#54792

PR Close angular#54914
@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 Apr 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: adev Angular.dev documentation good first issue An issue that is suitable for first-time contributors; often a documentation issue. help wanted An issue that is suitable for a community contributor (based on its complexity/scope). P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent state: has PR
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants