Try searching your code with the following regular expression:
[^\x00-\x7f]| { | |
| "env": { | |
| "browser": true, | |
| "es6": true, | |
| "mocha": true, | |
| "node": true | |
| }, | |
| "extends": ["eslint:recommended"], | |
| "globals": { | |
| "expect": true, |
Try searching your code with the following regular expression:
[^\x00-\x7f]| { | |
| minifySvg: false, | |
| collapseWhitespace: 'conservative' | |
| } |
| import uuid | |
| import json | |
| # Returns a python dictionary given a file containing a JSON-based | |
| # component definition. Every definition *must* contain a 'type' | |
| # and 'schema' field inside a top-level dictionary. Here is an | |
| # example of a simple schema file that defines a 'meta' component | |
| # containing a 'name' field. | |
| # |
In the last few yers, the number of programmers concerned about writting structured commit messages had dramatically grown. As exposed by Tim Pope in article readable commit messages are easy to follow when looking through the project history. Moreover the AngularJS contributing guides introduced conventions that can be used by automation tools to automatically generate useful documentation, or by developpers during debbuging process.
This document borrow some concepts, conventions and even text mainly from these two sources, extending them in order to provide a sensible guideline for writing commit messages.
A non-exhaustive list of WebGL and WebGPU frameworks and libraries. It is mostly for learning purposes as some of the libraries listed are wip/outdated/not maintained anymore.