All libraries have subtle rules that you have to follow for them to work well. Often these are implied and undocumented rules that you have to learn as you go. This is an attempt to document the rules of React renders. Ideally a type system could enforce it.
A number of methods in React are assumed to be "pure".
On classes that's the constructor, getDerivedStateFromProps, shouldComponentUpdate and render.
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <base href="app://./" /> | |
| <meta http-equiv="Content-Security-Policy" content="script-src 'self' app:; object-src 'self' app:;"> | |
| <script type="module" src="./module.js"></script> | |
| </head> | |
| <body> | |
| Check the console! |
| /** | |
| waitLatestFrom(...sources, [selector]) | |
| Like withLatestFrom but waits for all sources to produce at least one value | |
| before emitting. Emits immediately once it has a value for all sources. After | |
| that it actively collects the latest emission from the other source observables | |
| in the background and emits the latest collected values whenever the primary | |
| source emits -- like withLatestFrom. | |
| If the primary source completes, the other sources will be completed as well. |
| import requests | |
| from requests.auth import HTTPBasicAuth | |
| import re | |
| from StringIO import StringIO | |
| JIRA_URL = 'https://your-jira-url.tld/' | |
| JIRA_ACCOUNT = ('jira-username', 'jira-password') | |
| # the JIRA project ID (short) | |
| JIRA_PROJECT = 'PRO' | |
| GITLAB_URL = 'http://your-gitlab-url.tld/' |
We dropped Lerna from our monorepo architecture in PouchDB 6.0.0. I got a question about this from @reconbot, so I thought I'd explain our reasoning.
First off, I don't want this post to be read as "Lerna sucks, don't use Lerna." We started out using Lerna, but eventually outgrew it because we wrote our own custom thing. Lerna is still a great idea if you're getting started with monorepos (monorepi?).
Backstory:
List some crypto libraries for JavaScript out there. Might be a bit out dated. Scroll to the bottom.
http://www.w3.org/TR/WebCryptoAPI/
This specification describes a JavaScript API for performing basic cryptographic operations in web applications, such as hashing, signature generation and verification, and encryption and decryption. Additionally, it describes an API for applications to generate and/or manage the keying material necessary to perform these operations. Uses for this API range from user or service authentication, document or code signing, and the confidentiality and integrity of communications.
| from tastypie.fields import ToOneField | |
| from resources_base import CustomModelResource, ChildResource | |
| from models import User, Post | |
| class UserResource(CustomModelResource): | |
| class Meta: |