I've been thinking a lot about state and how to store data in Angular applications. Yesterday I gave a talk about unit testing in AngularJS and Angular 2. The people there are really liked the talk, but afterwards I learned that at the company whose office I was at (AWeber) they were creating all their new applications with React. I had seen a few high profile job postings mention React so even though I love Angular I wanted to not look like a fool in an interview. Also, I was curious how React components were similar and different from Angular components. And finally, I see the advanced Angular devs getting really excited about Redux so I wanted to figure out 1. what was so great about it, 2) why I would even want to use it in Angular, and 3) what the code looks like to actually use it! This post is just me getting my thoughts out as I try to understand React and Redux better. Maybe it could help you understand them better as well.
While working on a project for work I was presented with a plan to incorporate an animated jquery slider in our AngularJS application. I was able to wrap it in a directive and have every working honky-dory on gulp serve, but when I ran gulp build the jquery carousel widget wasn't working properly. It turned out that there were relative path references to other html, css, and JavaScript files declaring right there in the code with relative script tags. These import references were broken when the gulp build task did it's thing with minifying, uglifying, and concatenating files. Instead of going in and modifying the third party code, I was able to add these third party files into the project while keeping just these files safe from the build task.
I have a new friend on Linkedin, a Googler named Jon Youshaei. This is his latest post that appeared in my Linkedin feed and really got me thinking about creativity and imitation:
If you use the page object pattern when setting up e2e tests (as they are written in the gulp-angular yeoman generated project) then you might want to check that the properties of this page object are actually elements that exist on your page. Indeed, checking that my page object elements exist is almost always the first protractor test that I write. I naively tried a method that didn't work so great at first before finally finding the glorious "isPresent()" method available on my page object elements.
|
AuthorThe posts on this site are written and maintained by Jim Lynch. About Jim...
Categories
All
Archives
March 2023
|