Set which editor git should use.
This is the program that will open during a commit with no -m flag, a merge, a rebase, etc...
Select from any installed editor. Examples:
- emacs:
emacs - vi:
viorvim
| /** | |
| * Initialize your data structure here. | |
| */ | |
| var MyLinkedList = { | |
| head: null, | |
| length: 0, | |
| Node: function (val){ | |
| return { |
| # Reference: https://www.exclamationlabs.com/blog/continuous-deployment-to-npm-using-gitlab-ci/ | |
| # GitLab uses docker in the background, so we need to specify the | |
| # image versions. This is useful because we're freely to use | |
| # multiple node versions to work with it. They come from the docker | |
| # repo. | |
| # Uses NodeJS V 9.4.0 | |
| image: node:9.4.0 | |
| # And to cache them as well. |
| // This is an example of how to fetch external data in response to updated props, | |
| // If you are using an async mechanism that does not support cancellation (e.g. a Promise). | |
| class ExampleComponent extends React.Component { | |
| _currentId = null; | |
| state = { | |
| externalData: null | |
| }; |
| // This is an advanced example! It is not intended for use in application code. | |
| // Libraries like Relay may make use of this technique to save some time on low-end mobile devices. | |
| // Most components should just initiate async requests in componentDidMount. | |
| class ExampleComponent extends React.Component { | |
| _hasUnmounted = false; | |
| state = { | |
| externalData: null, | |
| }; |
| import { ImmutableArray } from './immutable-array'; | |
| describe('ImmutableArray', function() { | |
| let abc; | |
| beforeEach(() => abc = ['A', 'B', 'C']); | |
| it('clone() should create a shallow copy of the array', function() { | |
| const result = new ImmutableArray(abc).clone(); | |
| expect(result).toEqual(['A', 'B', 'C']); |
Set which editor git should use.
This is the program that will open during a commit with no -m flag, a merge, a rebase, etc...
Select from any installed editor. Examples:
emacsvi or vimA complete list of RxJS 5 operators with easy to understand explanations and runnable examples.
When working with Git, there are two prevailing workflows are Git workflow and feature branches. IMHO, being more of a subscriber to continuous integration, I feel that the feature branch workflow is better suited, and the focus of this article.
If you are new to Git and Git-workflows, I suggest reading the atlassian.com Git Workflow article in addition to this as there is more detail there than presented here.
I admit, using Bash in the command line with the standard configuration leaves a bit to be desired when it comes to awareness of state. A tool that I suggest using follows these instructions on setting up GIT Bash autocompletion. This tool will assist you to better visualize the state of a branc