Pascal Küsgen

Web Developer

[Pascal Küsgen @Pascalmh]

@laforge_toma @tan_stack @TkDodo The cache should probably be cleared on logout, otherwise on a shared device a user could get access to the cached data of the previous user. That said there's no benefit in adding the user-id to the cache, right?

[Pascal Küsgen @Pascalmh]

@solarpapst @elonmusk The Screenshot seems to show a Chat in WhatsApp.

[Pascal Küsgen @Pascalmh]

@kentcdodds Where would you plug it in once you're there?

[Pascal Küsgen @Pascalmh]

@maxlynch @nextjs https://t.co/VtDtknXQhx by @jherr might be interesting - there's also a Video about it on YT: https://t.co/Q81jnqRHod

[IP @ipwanciu]

Three steps to use Angular signal inputs now 💪🏼

PS. Was tested on a small project, don't do it in production! 🫤

#Angular #ngxtension

[Daniel Glejzner @DanielGlejzner]

Frontend Unit Tests.

🟡 The Gold Standard 🟡

Everyone racing for top coverage.
But reality looks much much different.

When NOT to Write Frontend Unit Tests:

• PoCs/MVPs: Here today, irrelevant tomorrow.
• UI part that is changed a lot: Don't waste your time.
• Experimental features: Can change any minute.
• Basic static components: Not worth it.
• Overwhelming mocking: Value > Effort.
• Deadlines: Especially in startups.
• Limited resources: Business value first/early phase.
• Redundant scenarios: 100% coverage is not the goal.
• Backend is more important: Frontend is changing much more often.

When TO Write Frontend Unit Tests:

• Critical features: Some things just can't fail.
• Complex logic: Once stable of course.
• Reusable components: The Foundation.
• Regression prevention: When it breaks often.
• Set in stone features: Worth the effort.
• Documentation: Tests can be great for that.
• Pre-refactoring: Before embarking on refactoring.
• Integration points: Vulnerable places.

Business Perspective:

• User Focus: E2E reflecting customer experience.
• Cost Efficiency: E2E tests can catch critical bugs.
• Time Savings: Reducing emphasis on unit tests can speed up development cycles.
• Real-world Relevance: E2E tests in near-production environments offer tangible insights.
• Simplified Reporting: E2E results are often more digestible for non-technical stakeholders.
• Coverage Overkill: Extensive unit tests can be redundant with a strong E2E suite.
• Maintenance Overhead: Frontend changes might require frequent unit test updates.

Businesses often lean towards ROI.
E2E tests often provide clearer value.

[Pascal Küsgen @Pascalmh]

@BHolmesDev @housecor Tesla also has an App to plan trips, not sure if there's something similar for Hyundai. https://t.co/JHepJZCSWW

[Pascal Küsgen @Pascalmh]

@BHolmesDev @housecor At least in Germany - no you don't. There are usually other providers on site of a supercharger as well and Tesla superchargers are opened up to non-tesla vehicles as well. You can check an App like https://t.co/RY11YlxjMO to see where chargers are.

[Pascal Küsgen @Pascalmh]

@goetzrobin Is there a (getting started) guide on how to contribute a Component? If not, a Video of someone implementing a new spartan/ui component would be really helpful!

[Pascal Küsgen @Pascalmh]

@juristr Why is there an extra new line added to the package.json? 🙈 I keep seeing that in your videos and while using nx myself.

[Pascal Küsgen @Pascalmh]

@_ng_news @mgechev @Jean__Meche @laforge_toma Thanks Rainer (lovely new Thema by the way)!
FYI: The Code of the https://t.co/0vBGcYsadd App can be found here: https://t.co/ge33cPgeZY

[Pascal Küsgen @Pascalmh]

@housecor @gioragutt Mostly yes. Sometimes you want elements to be grouped together, other times they should be separated by an empty line.

label[for=foo]
input#for
span.errorMessagesForFoo
label[for=bar]
input#bar

I'd like to see a free line before the label for the 2nd input

[Pascal Küsgen @Pascalmh]

@ipwanciu There's a "no-restricted-imports" rule in eslint.

[Mike Pearson @mfpears]

The web development industry almost entirely missed the point of Flux and unidirectionality. Most modern React, SolidJS, etc apps are MVC. Which isn't a problem for simple apps. But when features have to be complex, it helps to know the most fundamental lessons of the industry.

[Pascal Küsgen @Pascalmh]

@Enea_Jahollari @laforge_toma The "Observable-Method" doesn't work with Cypress Component Testing at the moment - there's an open Issue (thanks @yjaaidi) here: https://t.co/m08AVwAimX

[Pascal Küsgen @Pascalmh]

@ja_seifert @DanielGlejzner There's this: https://t.co/XZf5C5AKe0 - it seems a little outdated but the "postUpgradeTasks" should be a good start for your own config https://t.co/LhiqdAviz3

[Edouard Bozon @edbzn]

👉 Official @playwrightweb's Component Testing support for Angular is a work in progress.

https://t.co/Oubbt7XzIu

[Pascal Küsgen @Pascalmh]

@housecor Just found one it.only in our tests 🙈 Thanks for sharing!

[Pascal Küsgen @Pascalmh]

@bradzacher @renovatebot Where is it configured? I don't see a renovate.json in the repo?

[Thomas 🅰️🇨🇵 @laforge_toma]

🔔I’m available for new challenges.

I’m currently seeking new challenges as an Angular Frontend Engineer. I am eager to contribute to your team's success by ensuring faster delivery and a successful Angular application. My expertise lies in best practices, performance optimization, architectural design, and training.

👉 Available immediately
👉 Expertise in: Angular / TS / NgRx / RxJs / Nx
👉 Open to full remote or hybrid positions in the Grenoble area

🙏 RT is highly appreciated 🙏

✅ Visit my personal website: https://t.co/vg4tY89N5W
✅ Check out my current project for the Angular community: AngularChallenges on GitHub: https://t.co/o8uXhDasxF

If you would like more information or wish to connect with me, please feel free to reach out to me on X or via email at [email protected].

I look forward to taking on new challenges with you! 🚀