nguyentu9

src
├─ app
│  ├─ API (Module)
│  │  ├─ main (Folder)├─ Base(provider)
│  │  |               ├─ licenses
|  |  │               ├─ permisstion
│  │  ├─ api (Base)
│  │  └─ ...
│  │
│  ├─ Service (All service)

nguyentu9

# Redis Cheatsheet
# All the commands you need to know


redis-server /path/redis.conf  # start redis with the related configuration file
redis-cli                      # opens a redis prompt


# Strings.

nguyentu9

export enum RxJsLoggingLevel {
  TRACE,
  DEBUG,
  INFO,
  ERROR
}

let rxjsLoggingLevel = RxJsLoggingLevel.INFO;

export function setRxjsLoggingLevel(level: RxJsLoggingLevel) {

nguyentu9

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---

nguyentu9

<input type="file" class="file-upload" onchange="console.log(event.target.files)">
  

nguyentu9

Advanced Component Patterns

Also, check out Advanced Angular Component Patterns on Egghead!

* Titles subject to change

React	Angular
Introducing Advanced React Component Patterns	00 Introducing Advanced Angular Component Patterns (egghead)
Build a Toggle Component (source)	01 Build a Toggle Component (stackblitz) ([egghead](https:

nguyentu9

RXJS and Hooks, a most unlikely union

State management is hard. It's one of those things there are a lot of great solutions out there for in the Javascript library ocean, but none are a 1-size-fits-all, especially when it comes to approaching medium-to-large size apps with some semblance of sanity. I'd like to share some of the things we've learned here at Reonomy in our heroic rewrite of our old Angular 1.7 app to a new React one, and I'd like to particularly focus on how we found a way to get hooks and observables to play nice with each other (audience gasps). I know, a crazy thought.

The ideal world is a totally self-enclosed component

Isn't it a beautiful thing when a component does one thing, does it well, can be placed anywhere, and manages only its own state? Maybe it even has its own backend API with its own CRUD definitions, neatly Typed. These are the kinds of components you reread your own GitHub pull request code for over and over, at the end of the day, accompanied by a glass of whiskey

nguyentu9

// --------------------------------------------------
// Flexbox SASS mixins
// The spec: http://www.w3.org/TR/css3-flexbox
// --------------------------------------------------

// Flexbox display
@mixin flexbox {
  display: -webkit-box;
  display: -moz-box;
  display: -ms-flexbox;

nguyentu9

Nx

https://nx.dev/

Nx is a suite of powerful, extensible dev tools to help you architect, test, and build at any scale — integrating seamlessly with modern technologies and libraries while providing a robust CLI, caching, dependency management, and more.

It has first-class support for many frontend and backend technologies, so its documentation comes in multiple flavours.

Principles

nguyentu9

static int modInverse(int a, int n) 
	{
	    int i = n, v = 0, d = 1;
	    while (a>0) {
	        int t = i/a, x = a;
	        a = i % x;
	        i = x;
	        x = d;
	        d = v - t*x;
	        v = x;