| { | |
| "editor.rulers": [130], | |
| "workbench.colorTheme": "Default Light+", | |
| "workbench.colorCustomizations": { | |
| "editorRuler.foreground": "#eaeaea" | |
| } | |
| } |
After developing a feature in a branch, the next step is to submit a Pull Request (PR), to merge your changes into the master branch.
After submitting a PR, the PR page may show [C] on one or more files, indicating conflicts between your feature branch and the current version of the master branch.
Rebasing your branch's changes on top of the latest version of the master branch helps ensure that your code won't destabilise the code in the master branch, when it is merged into it.
Source: https://confluence.atlassian.com/bitbucket/set-up-an-ssh-key-728138079.html
ssh-keygen/Users/name/.ssh/id_rsa)
My Gulp build script does various things including linting code and packaging releases.
I'd like to extend this script, so that it can be reused by all of my different repos. This necessitates adding unit tests, so that I can be sure that the expected environment and config result in the right files being generated into the correct locations.
This testing is proving very difficult, as, when running shell commands from Node using execa, both Gulp and Mocha are adding layers of abstraction. These make it hard to see when tests are failing and why.
The solution seems to be to remove the abstraction by using raw shell commands in my npm scripts. So now I'm migrating my build script from Gulp to NPM.
| /** | |
| * @function debuggerOnAttributeMutation | |
| * @summary Open the JavaScript debugger when a particular attribute is mutated on the target element. | |
| * @public | |
| * | |
| * @param {boolean} debugMode - Whether debug mode is enabled (_options.debug) | |
| * @param {external:jQuery} $elements - One or more elements to watch the attributes of | |
| * @param {string} attribute - Attribute to watch for mutations on. | |
| * @see {@link https://developer.mozilla.org/en-US/docs/Web/API/MutationObserver} | |
| */ |
| // some-component.js | |
| // see https://www.youtube.com/watch?v=pOfwp6VlnlM. | |
| /** | |
| * @file Do something | |
| * @author [email protected] | |
| * @requires jquery.js | |
| */ | |
| /** |
Animating with requestAnimationFrame Since the interval parameter is irrelevant in complex animations, as there’s no guarantee that it will be honored, a new API has been designed: requestAnimationFrame. It’s simply a way to tell the browser “before drawing the next frame on the screen, execute this game logic/animation processing”. The browser is in charge of choosing the best moment to execute the code, which results in a more efficient use of resources[3].