Angular + NGRX Architecture: When To Use Component State Vs NGRX State
How do you decide when a piece of information should go in your NGRX store, as opposed to being maintained as local component variables?
How do you decide when a piece of information should go in your NGRX store, as opposed to being maintained as local component variables?
It’s easy to mock up emissions from your NGRX store over time in your unit tests, but the manner in which you do so is not immediately obvious from reading the NGRX testing documentation. In this post I’ll explain my thought process in how I solved this problem in the hopes that it helps others.
When using SQL Server to maintain your configuration and operational store for IdentityServer4, it’s fairly simple to tell IdentityServer to use a specific custom schema and custom table names. The process is similar to the way one configures ASP.NET Core Identity to use custom table names.
ASP.NET Core Identity is a very useful tool which provides a simple interface for user management. The default out-of-the-box implementation involves using Microsoft’s default table names and using a string (which defaults to a guid) for primary keys. If you don’t like these defaults it’s fairly simple to change the table names and schema and to use an auto-incrementing integer as a primary key.
ShareReplay is an RXJS operator which is very useful for managing expensive cold observable operations, sharing the source observable for concurrent subscribers, and replaying the result to subsequent subscribers without performing the operation again. It works by…
PrimeNG is a capable open source Angular UI library which provides a large number of useful components. There are plenty of premium themes available for PrimeNG, some of which do look rather nice. They also offer a commercial theme designer product. However, for those of us who wish to take the free, open-source route, the options are limited, which is ironic considering that the library itself is under the MIT license…
The private NuGet package feed included with Visual Studio Team Services provides a straightforward way to distribute proprietary NuGet libraries for use by multiple .NET applications within your organization without publishing your sensitive proprietary library publicly over the internet for all to use. Microsoft provides good documentation for how to do this in Windows, but I had to do some digging and troubleshooting in order to get it working in Linux. Once you figure it out it’s fairly simple, but…