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

Added two pages angular defer loading and control flow in angular #48

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

pawanpatil08
Copy link

No description provided.

@netlify
Copy link

netlify bot commented Jul 22, 2023

Deploy Preview for charming-faun-72b6b3 failed.

Name Link
🔨 Latest commit 2c611f7
🔍 Latest deploy log https://app.netlify.com/sites/charming-faun-72b6b3/deploys/64c880375e3a4e00071e023f

@santoshyadavdev
Copy link
Owner

Thank you @pawanpatil08 I will review this, I need to check why build is failed

"avatar_url": "https://avatars.githubusercontent.com/u/16464034?v=4",
"profile": "https://github.com/pawanpatil08",
"contributions": [
"code"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"code"
"doc"

Snippet submissions fall under the "doc" category of contributions.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

any specific reason for this

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done @ajitzero

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"code" is for project logic changes, e.g., adding a feature like a theme toggle, fixing bugs like rendering issues, etc.

A snippet/article is a documentation change.

Here's the full table of keywords with description: https://allcontributors.org/docs/en/emoji-key

The best fit is the "content" category, but it isn't used as much, so everything unrelated to code falls under "docs".

README.md Outdated
@@ -88,6 +90,8 @@ pnpm preview
<td align="center" valign="top" width="14.28%"><a href="https://github.com/lucioaimar"><img src="https://avatars.githubusercontent.com/u/64326713?v=4?s=100" width="100px;" alt="Lucio Aimar"/><br /><sub><b>Lucio Aimar</b></sub></a><br /><a href="https://github.com/santoshyadavdev/angular-snippets/commits?author=lucioaimar" title="Documentation">📖</a></td>
<td align="center" valign="top" width="14.28%"><a href="https://github.com/deepakrudrapaul"><img src="https://avatars.githubusercontent.com/u/25549935?v=4?s=100" width="100px;" alt="Deepak Rudra Paul"/><br /><sub><b>Deepak Rudra Paul</b></sub></a><br /><a href="https://github.com/santoshyadavdev/angular-snippets/commits?author=deepakrudrapaul" title="Documentation">📖</a></td>
<td align="center" valign="top" width="14.28%"><a href="https://github.com/rubenperegrina"><img src="https://avatars.githubusercontent.com/u/23550574?v=4?s=100" width="100px;" alt="Rubén Peregrina"/><br /><sub><b>Rubén Peregrina</b></sub></a><br /><a href="https://github.com/santoshyadavdev/angular-snippets/commits?author=rubenperegrina" title="Documentation">📖</a></td>
<td align="center" valign="top" width="14.28%"><a href="https://github.com/pawanpatil08"><img src="https://avatars.githubusercontent.com/u/16464034?v=4?s=100" width="100px;" alt="Pawan Patil"/><br /><sub><b>Pawan Patil</b></sub></a><br /><a href="https://github.com/santoshyadavdev/angular-snippets/commits?author=pawanpatil08" title="Code">💻</a></td>

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This part should be auto-generated from .all-contributorsrc, so this shouldn't be manually committed.

@@ -0,0 +1,83 @@
---
title: Build in control flow upcoming Angular
Copy link
Contributor

@ajitzero ajitzero Jul 31, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
title: Build in control flow upcoming Angular
title: Built-in control flow in upcoming Angular

Typo

{/if}
```

link for RFC : https://github.com/angular/angular/discussions/50719
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As you've rightly pointed out here, this is still an RFC and is open to change. I think we should hold off on this until it's confirmed and out in Angular 17 (probably)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct that why added the upcoming in angular

@@ -0,0 +1,64 @@
---
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same point here. Please push this off until the RFC is closed, and we actually have an initial implementation.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@santoshyadavdev Can you Suggest here,

contributedBy: "@pawanpatil08"
---

as a part of our ongoing work on implementing the Signals RFC,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see a lot of minor grammar issues / non-capital letters. Please run this through Grammarly or Google Docs since your actual content is well-written but has many obvious issues which can be fixed automatically.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey, @ajitzero tried it in Google Docs.
please suggest the any mistake in this file

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated.

Copy link
Author

@pawanpatil08 pawanpatil08 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, @santoshyadavdev ,
Can you please review the changes and let me know about Ajit's suggestion?

"avatar_url": "https://avatars.githubusercontent.com/u/16464034?v=4",
"profile": "https://github.com/pawanpatil08",
"contributions": [
"code"
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done @ajitzero

contributedBy: "@pawanpatil08"
---

as a part of our ongoing work on implementing the Signals RFC,
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey, @ajitzero tried it in Google Docs.
please suggest the any mistake in this file

@@ -0,0 +1,64 @@
---
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@santoshyadavdev Can you Suggest here,

@@ -1,7 +1,9 @@
# Angular Snippets

<!-- ALL-CONTRIBUTORS-BADGE:START - Do not remove or modify this section -->
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove this file from the PR since the comment explicitly asks to have no changes. These whitespace are probably fine but pointless to add them.

@@ -0,0 +1,83 @@
---
title: Built-in control flow in upcoming Angular
description: "Build in control"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
description: "Build in control"
description: "Built-in control"

- Syntactically distinct from HTML syntax.
- Works across multiple templates (if-elseif-else, switch-case-default), including template type-checking.
- Flexible syntax allowing customization for each use case (if vs for vs switch).
Address common pain points.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Address common pain points.
- Address common pain points.

{:case x}
X case
{:case y}
Y case
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This syntax is not finalized in the RFC since, in the replies, it has been pointed out that they may support multiple cases in one line: {:case x, y}

This is part of the reason I suggest keep this snippet as a draft until the features are actually out.

{/if}
```

### if block - conditionals
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### if block - conditionals
### if block - Conditionals

contributedBy: "@pawanpatil08"
---

as a part of our ongoing work on implementing the Signals RFC,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
as a part of our ongoing work on implementing the Signals RFC,
As a part of our ongoing work on implementing the Signals RFC,

---

as a part of our ongoing work on implementing the Signals RFC,
we’ve known that the existing zone-based control flow directives would not be able to function in zoneless applications.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
we’ve known that the existing zone-based control flow directives would not be able to function in zoneless applications.
We've known that the existing zone-based control flow directives would not be able to function in zoneless applications.

as a part of our ongoing work on implementing the Signals RFC,
we’ve known that the existing zone-based control flow directives would not be able to function in zoneless applications.
We will need to implement reactive control flow for zoneless applications.
We considered modifying the existing control flow directives to support zoneless applications as well,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
We considered modifying the existing control flow directives to support zoneless applications as well,
We considered modifying the existing control flow directives to support zoneless applications as well.

This entire paragraph is copied from different parts of the RFC. Please rewrite is slightly so the next line makes sense from the previous line. Again, Grammarly should be sufficient.


- Make deferred loading in Angular predictable and ergonomic for all developers
- Reduce initial page load time due to smaller initial bundle sizes
8 Support deferred loading of directives & pipes as well as components
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
8 Support deferred loading of directives & pipes as well as components
- Support deferred loading of directives & pipes as well as components

I am not sure about this, since "8" looks like a typo but the rest of the sentences don't seem to be related.

{/defer}
```

Will see you Built-In Control Flow in next snippets
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Will see you Built-In Control Flow in next snippets

This line makes no sense.

@santoshyadavdev
Copy link
Owner

Thank you both I am trying to figure out the build issue, I will soon review the PR

@santoshyadavdev
Copy link
Owner

ing the Signals RFC,

Hi @pawanpatil08 thank you for PR. Let me know once you take care of comments from @ajitzero, also if you can update the branch from main that would be greatt.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants