jonathanroehm

Setting up your bundle config to allow your host app to use the local version of your gem

What we don't want:

Having to test your gem on your host app after having to commit changes to your gem... and then having to rebundle your gemfile ... which forces you to refer to your gem-in-process like:

gem 'nfg_ui', git: 'https://github.com/network-for-good/nfg_ui', branch: 'feature/some_feature_branch_that_im_working_on'

And then have to:

$ bundle update gem_name`

jonathanroehm

# In `your_engine/Gemfile` add the pertinent spring gems:
# Note, do not add spring gems as `spec.add_development_dependency`'s in your gemspec. 
source 'https://rubygems.org'
git_source(:github) { |repo| "https://github.com/#{repo}.git" }

gemspec

group :development do
  gem 'spring'
  gem 'spring-watcher-listen'

jonathanroehm

# assets/javascripts/vendors/flatpickr.coffee
# Flatpickr is set with a f.input :obj, data: { toggle: 'flatpickr' }

start = ->
  $("[data-toggle='flatpickr']").flatpickr
    altInput: true

document.addEventListener('turbolinks:load', start)

jonathanroehm

.form-control.flatpickr-input{
  &:disabled, &[readonly]{ background-color: #fff; }
}

// Be explicit on aria-invalid instead of pseudoclass :invalid / :valid
// Will allow error state to show on inputs like select2 and flatpickr
.form-control[aria-invalid='true']{
  .was-validated & + .flatpickr-input,
  .was-validated &{
    border-color: $form-feedback-invalid-color;

jonathanroehm

// OSX Location: /Users/[username]/Library/Application Support/Sublime Text 3/Packages/User/RubyTest.sublime-settings

// To access RubyTest's user settings in Sublime Text 3: 
// Sublime Text > Preferences > Package Settings > RubyTest > Settings - User

// Hot Keys when editing a (spec) file:
// Cmd + Shift + R -- Test this line
// Cmd + Shift + T -- Test this document
// Cmd + Shift + E -- Re-run previous test (can be executed from any file, does not need to be the spec file in question)