So… how do you create and use a Ghost animation in your Angular application?
In this article, I’m going to give you the code, demos, screenshots and whole shebang on how to create a basic Ghost table animation that you can adapt for your Angular project.
With the help of Angular’s amazing CLI we’ll create a new component called ghost-table. Here’s how you do it.
ng generate component ghost-table
Give it a few seconds to whirl its magic.
Important Note To keep this article as simple as possible I’ve opted to use an Angular component. However, I do not recommend this approach with any type of production application. You should instead use an Angular module to hold the Ghost table animation and then import it into the other modules of your Angular application. …
Hunting for an Angular book that will help you rocket your Angular expertise?
Fortunately there are oodles of options to choose from and stacks of Angular books for beginners, for intermediates and experts.
The best part is that there are some henkity-cool choices — Angular books written by top-notch consultants, ex-Googlers, etc…
Not to mention that some of the books out there even have reviews from the folks on the Angular team.
But sorting through all the options to find the perfect one for YOU can be overwhelming.
That’s why I put together a list of the best Angular books of 2021 for you. …
Some web apps act like a dying cow.
And would you believe it? These silly-jiggy-jaggy-dancing spinners seem to think they’ll hypnotize us into patiently waiting those extra 6.8 seconds!
It’s like waiting on a turtle for a horse ride.
Say, can’t we do better?
How can we find the HTTP requests in our Angular application that are slowing the show? Once we’ve uncovered the bottle-necks we can fix them and make your HTTP requests zip.
We could then connect our Angular app to a monitoring service like Application Insights and get alerts for turtle-performance.
Why just imagine it! About the time your boss shows up saying that users are complaining of slowness you’d tell him “I just got done fixing it!” and he’d be so surprised he’d swallow his gum. …
Why is it such common scenario?
The project you’re sweating over is becoming a smashing success and you’re ready to be done… but all of a sudden at the last minute there’s this change to that form that must happen NOW!
And the demands of your boss or client are clutching you tighter and tighter.
These kinds of scenarios are way too common. So how about a proactive approach that will allow us to dynamically render an Angular form? And make our form roll with the punches that way we can take it easy?
How about we build a dynamic Angular form so that we can throw it a blob of JSON or some other common schema that it can render? …
Dancing in your pants to build a dynamic form with Angular?
In this article we’ll work with a simple example, taking a JSON blob and using it to dynamically render a reactive Angular form.
The JSON blob will keep our examples simpler but it’s your project so do what you want, make an HTTP call to your API server for the JSON blob, compile the JSON file with the app, or even…
…wrap it up in a sock and hurl it into the toilet.
JSON blobs and dynamic forms. Uh… let’s get started.
## Our JSON…
With the growing power and fame of the .NET Core framework and Angular some awesome possibilities are blooming.
One of these is .NET Core’s support for Angular.
Just take the .NET Core CLI and the only thing you gotta bang into that keyboard is…
dotnet new angular -o MyNextAwesomeApp
…and BOOM! It generates a simple .NET Core API server as well as an Angular SPA with amazing server-side rendering, auth options, and more.
Hot stuff if you want to know my opinion.
But what if we want to do better? And use NX to manage our Angular app(s)?
I mean, why not? All the other big guys…
How do you add feature flag functionality to your Angular application? In this guide we’ll explore 3 different ways and examine the pros and cons.
Ready? Let’s dive in. 👉🏻
This way is straightforward.
It’s as simple as ABC.
And easy as pie. Here’s how it works.
You can make use of the environment files to add feature flag capability to your Angular app.
Some experts might say that this is not a scalable way to tack on feature flags, and while they may be right, it’s still a great way to get started without bloating your app with an initialization service. Please keep in mind that it totally depends on your scenario. If you only have one or two feature flags that you flip on or off then this is a great option for you to consider. Does it scale? Nope. …
One of the most popular Angular questions on Stackoverflow is a question about how to use jQuery with Angular.
Say, what should you do?
Is it even okay to use jQuery AND Angular in the same project?
Alright. Let’s hold our britches….
…because before we go any further it’s important to understand the difference between Angular & jQuery.
It seems we get them confused and tangled together.
And when someone from a jQuery background comes to Angular they usually get this itch to revert to jQuery instead of harnessing Angular’s super-powers.
Beginning with jQuery.
jQuery is a library that simplifies DOM manipulation, event handling, CSS animation and AJAX. …
I remember as an Angular novice the mind-boggling thought of writing tests for my Angular apps.
And then later the guilty feeling of deploying an Angular app multiple times a day without any kind of tests.
Man oh man! Convincing me to write tests for an Angular application would’ve been like trying to force a toddler to eat their peas.
Now, I know I’m not the only guy on the block that used to think like this. Test syndrome is common.
But nail this and you’ll become a honking-powerful, test-cranking Angular wizard.
Installing and configuring Jest can be a thorny job. …
Say, anyone making their first attempt at writing tests for an Angular app might rather grab a drumstick and herd a mob of hairy cats down the street instead.
It’s easy to get lost trying to decide which pieces of the Angular application to test.
Er… what parts must I test and what can I skip?
Do we need 100% code coverage?
And should I be writing tests for that front-end UI stuff that’s always evolving? UI tests tend to be brittle so where should an Angular developer set their mouse traps? …