In React's terminology, there are five core types that are important to distinguish:
React Elements
| /** | |
| * Move events with a given title from your primary calendar to another calendar. | |
| * You must enable the Calendar Advanced Service: | |
| * https://developers.google.com/apps-script/guides/services/advanced#enabling_advanced_services | |
| */ | |
| function moveEvents(eventTitle, fromCalendarName, toCalendarName) { | |
| var fromCalendarId = CalendarApp.getCalendarsByName(fromCalendarName)[0].getId(); | |
| var toCalendarId = CalendarApp.getCalendarsByName(toCalendarName)[0].getId(); | |
| var now = new Date(); |
| // utilizes the browser eventsystem | |
| // usefull in cases where you need communication between independent components | |
| // registered events are automatically removed onunload with preserving any other onunload handler | |
| var eventsMixin = function(target) { | |
| var _subscriptions = []; | |
| target.broadcast = function(type, payload) { | |
| var ev = new CustomEvent(type, { | |
| detail: payload, |
In React's terminology, there are five core types that are important to distinguish:
React Elements
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
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
Uses capped collection, tailable cursors and streams.