- ...including Breaking Changes: https://github.com/facebook/create-react-app/releases/tag/v4.0.0
yarn add --exact [email protected]
yarn add react react-dom
class SprottyWrapper { | |
componentDidMount() { | |
// Diagramm erzeugen, wie in multicore.ts (hier stark gekürzt:) | |
this.processor = ...; | |
const modelSource = container.get<LocalModelSource>(TYPES.ModelSource); |
@@ -1,32 +0,0 @@ | |
#! /bin/bash | |
DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null 2>&1 && pwd )" | |
URL="https://fonts.googleapis.com/css?family=Nunito+Sans:300,300i,400,400i,600,600i,700,700i,800,800i,900,900i&display=swap" | |
http -p b "${URL}">${DIR}/fonts.css |
yarn add --exact [email protected]
yarn add react react-dom
My very subjective impressions and opinions about VS Code and IntelliJ mainly for TypeScript development.
Note 1: This is not an objective comparison, just a list of points that I noticed when working with the two tools, and which I liked better or worse in each case.
Note 2: For IntelliJ, I used IntelliJ Ultimate Edition 2020.3
Note 3: I have used VS Code for TypeScript much longer than IntellIJ so also for this reason, this is not a "fair" comparison, because many things will turn out only in the long run, if good or bad
Note 4: many/some of the differences maybe could be adjusted by changing settings and/or keyboard shortcuts. And of course by learning the tools better.
A Redux-based application holds a forest-like data structure, like Folders and Documents in a file system, but with many root Folders, like this:
In a React Component, DocumentList we display all Documents (all leafs of all trees) and when clicking on one Document, we need access to the Document's root (Folder) object (to read some information from it)
I recently (october 2020) evaluated MobX for a project as alternative to Redux (Redux Toolkit).
You can find my very subjective impressions below.
Redux DevTools better than MobX (for me they were more helpful when finding bugs)
Redux is more widely used than MobX
Change/Dependency tracking in MobX is powerful but not always obvious how it works (both behind the scene and in my application). If values didn't update where I expected it, finding the bug sometimes was hard
#! /bin/zsh | |
#xcode-select --install | |
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" |
query {
stories(first: 10) {
nodes {
id
title
excerpt
abstract class BaseError {
private final String message;
public BaseError(String message) { this.message = message; }
public String getMessage() { return this.message; }
}