Skip to content

Instantly share code, notes, and snippets.

🤑
Looking for work

Barney Carroll barneycarroll

🤑
Looking for work
Block or report user

Report or block barneycarroll

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
@barneycarroll
barneycarroll / README.md
Last active Apr 24, 2018
Of many sequential promises, only the last is worthy of consequence
View README.md

There are many scenarios where a particular interaction makes repeated calls to an asynchronous, and each subsequent call invalidates the previous. For example, typing in a field which can query an HTTP service for insights: if I type 'a', and wait long enough, a call should be sent to ask for pertinent suggestions; but if I'm still waiting on that response when I type 'b', then the results of the last call are impertinent. Only the last call's response should resolve.

Calling latest creates a 'promise debouncer' function. Either you pass in the async function there and then and call it without arguments, or you instantiate it empty and pass in the async function upon request. In either case, calling the function before its last promise has resolved will ensure that promise never resolves: only the last request will ever resolve.

@barneycarroll
barneycarroll / BornToDie.js
Created Apr 11, 2018
A component which redraws on post-creation & pre-removal, providing `{born, to, die,}` as flags to the supplied function
View BornToDie.js
const BornToDie = v => {
let
born = true,
to = false,
die = false,
let query
let draw
View Historian.js
const Historian = Object.assign(
Component => {
const histories = new WeakMap
return {
onbeforeupdate({}, old){
if(Component.onbeforeupdate && Component.onbeforeupdate.apply(this, arguments) === false)
return false
histories.set(old.state, old)
@barneycarroll
barneycarroll / broken.js
Last active Mar 10, 2018
Break a promise
View broken.js
const broken = (promise, state = {
pending: true,
settled: false,
resolved: false,
rejected: false,
value: undefined,
error: undefined,
}) => (
@barneycarroll
barneycarroll / README.md
Created Mar 2, 2018
When a nested expression is the desired return value
View README.md

Written to avoid the noisome pattern of

input => {
  const reference = expression with input

  sideEffects(reference)

  return reference 
}
View mimix.js
const {assign, keys} = Object
const scope = fn =>
function(){
return fn(x => x.apply(this, arguments))
}
const compose = (key, values) => (
key === 'view'
?
values.pop()
@barneycarroll
barneycarroll / 2mithril.es7.js
Created Jul 17, 2015
Convert DOM or XML/HTML to Mithril
View 2mithril.es7.js
const { map, reduce } = Array.prototype
const wrap = document.createElement( 'x' )
export const dom2mithril = dom =>
dom.nodeType === 3
? dom.nodeValue
: dom.nodeType === 1
? {
tag : dom.nodeName,
attrs : dom.attributes
@barneycarroll
barneycarroll / mithril-view-attrs.md
Created Feb 23, 2018
Work in progress: proposal for view attributes as a core mechanism in Mithril
View mithril-view-attrs.md

Precedent: render props (or, view attributes)

I've been toying the idea of 'view attributes' for a while, but over the past year they've taken off in the popular domain of React as 'render props'.

A component written to make use of view attributes is a 'view component' inasmuch as it doesn't have an opinion on downstream virtual DOM, but performs a useful function in the context of virtual DOM (whether that be transforming other attribute input, querying DOM or external references, providing state), which can be exposed via the view attribute provided to it.

Here's a sample of view components with associated demos.

The React community has already proved the far-reaching value of this concept to the point where the pattern is part of the official documentation, ahead of 'integrating with other libraries'. React Router

View NoopComponent.js
export const {
view: v => (
v.attrs.view
?
v.attrs.view.call(v.state, v)
:
v.children
)
}
@barneycarroll
barneycarroll / Blockm.js
Created Feb 22, 2018
A collection of view components for Mithril. A view component is one where the component provides no view of its own but instead accepts a view attribute which it then provides with data.
View Blockm.js
const callOBR = v =>
Promise.all(
['tag', 'attrs']
.map(x =>
v[x]
&& v[x].onbeforeremove
&& v[x].onbeforeremove.call(v.state, v)
)
)
You can’t perform that action at this time.