scottbarrow

This controller can be put on body or any other element.

1. Adds a websocket accessor to the element
2. Controller exposes a connected boolean getter
3. Controller bails with a warning if no shared consumer is available
4. Element will have data-action-cable-connected or data-action-cable-disconnected attributes which can be used for CSS selectors
5. Element will emit action-cable:connected or action-cable:disconnected events only when state is flipping
6. Errors => Disconnected to keep things simple

I intend to document the navigator.onLine accessor and the window:online/offline events so devs can handle PWA modes.

scottbarrow

<%= form_with(model: model, data: {controller: "reflex-form", reflex_form_reflex: "ExampleReflex#submit"}) do |form| %>
  <%= form.button data: {action: "click->reflex-form#submit"} %>
<% end %>

scottbarrow

// for this to work you need to set `"chromeWebSecurity": false` in cypress.json

describe('Make Stripe Payment', function() {
  before(function() {
    cy.visit('http://localhost:3000/en/stripe/checkout/')
    Cypress.Cookies.preserveOnce('sessionid')
  })

  it('should enter credit card details and finalise payment', function() {
    cy.get('[data-test="button-FormStripeCart-PayWithCreditCard"]').click()

scottbarrow

#!/usr/bin/env ruby

require 'open3'

#
# Adds RuboCop to a project, one cop per commit
#
class RuboCoper
  def run
    autocorrect_all

scottbarrow

Homebrew and Symlink Issues

if you see this:

Error: An unexpected error occurred during the `brew link` step
The formula built, but is not symlinked into /usr/local
Permission denied @ dir_s_mkdir - /usr/local/Frameworks
Error: Permission denied @ dir_s_mkdir - /usr/local/Frameworks

scottbarrow

While attempting to explain JavaScript's reduce method on arrays, conceptually, I came up with the following - hopefully it's helpful; happy to tweak it if anyone has suggestions.

Intro

JavaScript Arrays have lots of built in methods on their prototype. Some of them mutate - ie, they change the underlying array in-place. Luckily, most of them do not - they instead return an entirely distinct array. Since arrays are conceptually a contiguous list of items, it helps code clarity and maintainability a lot to be able to operate on them in a "functional" way. (I'll also insist on referring to an array as a "list" - although in some languages, List is a native data type, in JS and this post, I'm referring to the concept. Everywhere I use the word "list" you can assume I'm talking about a JS Array) This means, to perform a single operation on the list as a whole ("atomically"), and to return a new list - thus making it much simpler to think about both the old list and the new one, what they contain, and

scottbarrow

Make it real

Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.

Ship it

Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.

Do it with style