Separating State Into Angular Modules With Ngrx

In this post, I want to give you an explanation of the state tree of Ngrx if you are working with a state and how to separate it into different modules.
In this blog

One state for your entire application with forRoot(…)
Separating state into modules with forFeature(…)
Conclusion

If you are building smaller or large Angular application, you will sooner or later face the problem of managing the state of your application. It gets influenced by a lot of things around which can be a simple button triggering a service – maybe with an HTTP action – which will set your application in a different state.

Link: https://dzone.com/articles/separating-state-into-angular-modules-with-ngrx?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

Comparing Progressive JavaScript Frameworks: Angular and Vue.js

Vue.js, the open source JavaScript framework, helps build beautiful web interfaces. Its excellent features can be strongly leveraged when it is paired with other web tools. Nowadays, many developers are replacing Angular and React.js with Vue.js.
This brings us to the topic of the article – should I go for Vue or Angular?

Link: https://dzone.com/articles/comparing-progressive-javascript-frameworks-angula?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

What Is a Service in Angular and Why Should You Use it?

Angular Service:
Angular services are singleton objects which get instantiated only once during the lifetime of an application. They contain methods that maintain data throughout the life of an application, i.e. data does not get refreshed and is available all the time. The main objective of a service is to organize and share business logic, models, or data and functions with different components of an Angular application.
An example of when to use services would be to transfer data from one controller to another custom service.

Link: https://dzone.com/articles/what-is-a-service-in-angular-js-why-to-use-it?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

Top 10 JavaScript Errors From 1000+ Projects (and How to Avoid Them)

To give back to our community of developers, we looked at our database of thousands of projects and found the top 10 errors in JavaScript. We’re going to show you what causes them and how to prevent them from happening. If you avoid these “gotchas," it’ll make you a better developer.
Because data is king, we collected, analyzed, and ranked the top 10 JavaScript errors. Rollbar collects all the errors for each project and summarizes how many times each one occurred. We do this by grouping errors according to their fingerprints. Basically, we group two errors if the second one is just a repeat of the first. This gives users a nice overview instead of an overwhelming big dump like you’d see in a log file.

Link: https://dzone.com/articles/top-10-javascript-errors-from-1000-projects-and-ho-1

Creating an UploadService to Work with Flow.js and Ng-flow

Having the ability to upload files was an important requirement for a recent project. Users of the AngularJS application needed to include different types of images, including a standardized zip-file of images, to complete the tasks associated with the solution.
The flow.js framework and associated ng-flow AngularJS directive seemed to be a perfect fit for the upload requirements. Ng-flow is built on top of flow.js and provides a quick and easy implementation where end-users can select or drag-and-drop files onto the screen where they can be uploaded. If configured correctly, a ghost version of the images appears – showing a preview while the file(s) are being uploaded. Finally, event handling provides a mechanism where business logic could be applied (like checking for duplicates, valid image type and size, etc.) before the upload process begins.

Link: https://dzone.com/articles/creating-an-uploadservice-to-work-with-flowjs-and?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev

.NET Core 2.0, Angular 4, and MySQL Part 2

When starting a new project, does basic configuration matter? .NET Core configuration differs greatly from the standard .NET projects. We don’t have any more web.config files but, instead, we use the built-in Configuration framework that comes with .NET Core.
Therefore, having a good understanding of how to configure your project and how to configure services, which you will use until the end of the development process, is a must.

Link: https://dzone.com/articles/net-core-20-angular-4-and-mysql-part-2-code-maze?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fwebdev