| version: '3' | |
| services: | |
| database: | |
| image: 'mongo' | |
| container_name: 'my-mongo-container' # give your contatner a name | |
| environment: | |
| - MONGO_INITDB_DATABASE=your-database-name # database name you want to make | |
| - MONGO_INITDB_ROOT_USERNAME=my-container-root-username # set your container root username | |
| - MONGO_INITDB_ROOT_PASSWORD=secret # set your contatner root password | |
| volumes: |
Paste the following code into the console panel of the DevTools window of Chrome or Firefox.
The style sheet came from (Web Scraper)[http://webscraper.io/] plugin for Chrome
It is useful for analyse a page layout and you can extend it to select preferred dom elements.
function addStyleString(str) {
var node = document.createElement('style');
First, take a look at the ESLint rule documentation. Just skim it for now. It's very long and boring. You can come back to it later.
ESLint rules works on the AST (Abstract Syntax Tree) representation of the code. In short, this is a tree structure that describes the code in a very verbose form. ESLint walks this tree and rules can subscribe to be notified when it hits a specific node type, like a Literal type, which could be the "hello" part of const welcome = "hello";.
Go ahead and play around with some code in AST Explorer (Make sure the parser is espree). It's a great tool!
Here are some good articles on the subject (ignore the scaffolding parts):
Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.
If you use atom... download & install the following packages:
| { | |
| "plugins": [ | |
| "spellcheck" | |
| ], | |
| "rules": | |
| // Spellcheck | |
| // | |
| "spellcheck/spell-checker": ["warn", { | |
| "skipWords": [ | |
| // own names |
