(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.
| var tmp = null; | |
| $('###selector###').popover({ | |
| trigger: 'manual', | |
| title: 'testing', | |
| delay: {show:500, hide:100} | |
| }); | |
| $('###selector###').hover(function(){ | |
| clearTimeout(tmp); |
(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.
| require 'set' | |
| USED_CASSETTES = Set.new | |
| module CassetteReporter | |
| def insert_cassette(name, options = {}) | |
| USED_CASSETTES << VCR::Cassette.new(name, options).file | |
| super | |
| end | |
| end | |
| VCR.extend(CassetteReporter) |
| console.log('Loading event'); | |
| // Twilio Credentials | |
| var accountSid = ''; | |
| var authToken = ''; | |
| var fromNumber = ''; | |
| var https = require('https'); | |
| var queryString = require('querystring'); |
| # This file was generated by the `rails generate rspec:install` command. Conventionally, all | |
| # specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`. | |
| # The generated `.rspec` file contains `--require spec_helper` which will cause this | |
| # file to always be loaded, without a need to explicitly require it in any files. | |
| # | |
| # Given that it is always loaded, you are encouraged to keep this file as | |
| # light-weight as possible. Requiring heavyweight dependencies from this file | |
| # will add to the boot time of your test suite on EVERY test run, even for an | |
| # individual file that may not need all of that loaded. Instead, make a | |
| # separate helper file that requires this one and then use it only in the specs |
A complete list of RxJS 5 operators with easy to understand explanations and runnable examples.
| // https://github.com/alfonsomunozpomer/react-fetch-mock | |
| import React from 'react' | |
| import fetchMock from 'fetch-mock' | |
| import Enzyme from 'enzyme' | |
| import {shallow, mount, render} from 'enzyme' | |
| import Adapter from 'enzyme-adapter-react-16' | |
| Enzyme.configure({ adapter: new Adapter() }) |
You are writing a spec with type: :request, i.e. an integration spec instead
of a controller spec. Integration specs are wrappers around Rails'
ActionDispatch::IntegrationTest class. I usually write controller tests using
this instead of type: :controller, mainly because it exercises more of the
request and response handling stack. So instead of writing something like
get :index to start the request, you would write get books_path or similar.
One of the issues with using type: :request is that you lose the ability to
| name: Test | |
| on: | |
| push: | |
| branches: | |
| - main | |
| - features/** | |
| - dependabot/** | |
| pull_request: | |
| branches: |
| Parameters: | |
| App: | |
| Type: String | |
| Description: Your application's name. | |
| Env: | |
| Type: String | |
| Description: The environment name your service, job, or workflow is being deployed to. | |
| Name: | |
| Type: String | |
| Description: The name of the service, job, or workflow being deployed. |