❤4
Angular Munich
WHUT THE HELL?! ) That is interesting: The upcoming revised #Angular style guide will recommend adding an ng suffix to filenames. So, for example: • home.component.ng.html or home.component.ng.ts, • or even just home.ng.ts and home.ng.html. The idea is…
Horrible - Terrible - Unlackely - BOOOORING! WHYYYYYYYYYY?!?!?!?!?!
Cut the "*.service.ts" in favor of "*.ng.ts".
WHY? How I can manage by import? Import MyHero as Component or MyHero as a Service? or MyHero as Directive/etc...?
Then we need definitely a new Guidelines for folder structures?! Or? I think so...
Yes or No?
Cut the "*.service.ts" in favor of "*.ng.ts".
WHY? How I can manage by import? Import MyHero as Component or MyHero as a Service? or MyHero as Directive/etc...?
Then we need definitely a new Guidelines for folder structures?! Or? I think so...
Yes or No?
🤯3
Angular 19 introduces instant HMR, allowing styles and templates to be updated without reloading the entire app. This means that developers can see the effect of their changes immediately, making the development cycle much smoother and faster. Hot module replacement for styles is enabled by default in v19!
To try HMR for templates use:
NG_HMR_TEMPLATES=1 ng serve
To disable this feature specify
"hmr": false as a development server option, or alternatively use:ng serve --no-hmr
👆🏻 pfffff...
it's work terrible, horrible, AWFUL!
Just disable that... Please...
#ng19_1_1
Found something interesting...
CV+Letter or not CV+Letter, that the question...
And if Yes, then follow this recommendations... However in the comments there are more points with dos and don'ts
Link
CV+Letter or not CV+Letter, that the question...
And if Yes, then follow this recommendations... However in the comments there are more points with dos and don'ts
> a candidate doesn’t always have the expertise to do it because they are experts in the job they do, not experts in CV or letter writing.
Link
This media is not supported in your browser
VIEW IN TELEGRAM
Let’s go to the angular expert training! 🚅🚋🚋🚋🚋🚋🚋🚨
🔥1
Decisions that define us: navigating leadership in tech.
Link
Leadership is a lot like parenting. The scariest part isn't that we’ve grown into adults - it’s realizing we are the adults, the ones who must make the tough decisions and own the consequences. Are you ready to embrace that responsibility?
Link
He's not wrong! Is he?
If your backend team is dictating design or functionality, your priorities are backward. Your flow should look something like this:
Users → Product → Frontend → Backend → DevOps.
Users show Product what they need.
Product tells Frontend what they need to build.
Frontend tells Backend what data/logic they need to make it happen.
Backend keeps things efficient and scalable.
DevOps keeps it all running smoothly.
Get your house in order! 😅
If your backend team is dictating design or functionality, your priorities are backward. Your flow should look something like this:
Users → Product → Frontend → Backend → DevOps.
Users show Product what they need.
Product tells Frontend what they need to build.
Frontend tells Backend what data/logic they need to make it happen.
Backend keeps things efficient and scalable.
DevOps keeps it all running smoothly.
Get your house in order! 😅
👍1
Angular Munich
Horrible - Terrible - Unlackely - BOOOORING! WHYYYYYYYYYY?!?!?!?!?! Cut the "*.service.ts" in favor of "*.ng.ts". WHY? How I can manage by import? Import MyHero as Component or MyHero as a Service? or MyHero as Directive/etc...? Then we need definitely…
𝗦𝘂𝗺𝗺𝗮𝗿𝘆 𝗼𝗳 𝗦𝘁𝘆𝗹𝗲 𝗚𝘂𝗶𝗱𝗲 𝗥𝗙𝗖 𝗙𝗲𝗲𝗱𝗯𝗮𝗰𝗸 𝗮𝗻𝗱 𝗡𝗲𝘅𝘁 𝗦𝘁𝗲𝗽𝘀
𝗙𝗲𝗲𝗱𝗯𝗮𝗰𝗸 𝗦𝘂𝗺𝗺𝗮𝗿𝘆
• Positive Reception: Overall response to revising the style guide has been very positive.
• Naming and Suffixes Feedback:
• No mandatory statements on using “component,” “directive,” or “service” suffixes for class or file names in the style guide.
• Angular documentation and examples will avoid using these suffixes.
• Angular CLI schematics will still support configurable suffixes as per the original proposal.
𝗨𝗽𝗱𝗮𝘁𝗲𝗱 𝗥𝗲𝗰𝗼𝗺𝗺𝗲𝗻𝗱𝗮𝘁𝗶𝗼𝗻𝘀
• To better support tools like Prettier or Vite plugins:
• Angular Template Files: Use the .ng.html suffix.
• Angular TypeScript Files: Include .ng in filenames for imports from @angular/core, e.g., .ng.ts or .spec.ng.ts.
• This aids tooling in identifying Angular-specific files without parsing file contents.
𝗙𝗲𝗲𝗱𝗯𝗮𝗰𝗸 𝗦𝘂𝗺𝗺𝗮𝗿𝘆
• Positive Reception: Overall response to revising the style guide has been very positive.
• Naming and Suffixes Feedback:
• No mandatory statements on using “component,” “directive,” or “service” suffixes for class or file names in the style guide.
• Angular documentation and examples will avoid using these suffixes.
• Angular CLI schematics will still support configurable suffixes as per the original proposal.
𝗨𝗽𝗱𝗮𝘁𝗲𝗱 𝗥𝗲𝗰𝗼𝗺𝗺𝗲𝗻𝗱𝗮𝘁𝗶𝗼𝗻𝘀
• To better support tools like Prettier or Vite plugins:
• Angular Template Files: Use the .ng.html suffix.
• Angular TypeScript Files: Include .ng in filenames for imports from @angular/core, e.g., .ng.ts or .spec.ng.ts.
• This aids tooling in identifying Angular-specific files without parsing file contents.
Angular Munich
𝗦𝘂𝗺𝗺𝗮𝗿𝘆 𝗼𝗳 𝗦𝘁𝘆𝗹𝗲 𝗚𝘂𝗶𝗱𝗲 𝗥𝗙𝗖 𝗙𝗲𝗲𝗱𝗯𝗮𝗰𝗸 𝗮𝗻𝗱 𝗡𝗲𝘅𝘁 𝗦𝘁𝗲𝗽𝘀 𝗙𝗲𝗲𝗱𝗯𝗮𝗰𝗸 𝗦𝘂𝗺𝗺𝗮𝗿𝘆 • Positive Reception: Overall response to revising the style guide has been very positive. • Naming and Suffixes Feedback: • No mandatory statements on using “component,” “directive,” or…
𝗡𝗲𝘅𝘁 𝗦𝘁𝗲𝗽𝘀 𝗳𝗼𝗿 𝘁𝗵𝗲 𝗧𝗲𝗮𝗺
1. Create an updated revision incorporating feedback.
2. Begin tooling updates and develop opt-in refactoring tools for changes.
3. Collaborate with community tool maintainers to plan for the updated guide.
1. Create an updated revision incorporating feedback.
2. Begin tooling updates and develop opt-in refactoring tools for changes.
3. Collaborate with community tool maintainers to plan for the updated guide.
Quick tip after migrating to Angular 16 with standalone components!
If you're providing services directly in a component, you'll need to update your testing approach.
#unitesting
If you're providing services directly in a component, you'll need to update your testing approach.
#unitesting