Fabian Iwand

Results 288 comments of Fabian Iwand

Logo source: https://github.com/solidjs/solid-site/blob/main/public/img/logo/dark-without-wordmark/logo.svg According to archive.org the logo was still present on 2022-08-01: https://web.archive.org/web/20220801124138/https://www.solidjs.com/img/logo/dark-without-wordmark/logo.svg

> If I had to make an (uninformed) guess, I'd suspect the problem was introduced by https://github.com/solidjs/solid-docs/pull/163 Another candidate might be the migration to vite 3: https://github.com/solidjs/solid-site/pull/358

Workaround: ```js function datetimeInput({step, value, ...options} = {}) { const form = Inputs.datetime({value, ...options}); if(step == null) return form; form.date.step = step; if(value != null) { value = new Date(value);...

Slack thread: https://observablehq.slack.com/archives/C01LADG5CF6/p1633558706168700

I believe the ellipsis is not only a visual aid for long strings, but also avoids rendering excessively large strings in the DOM. Under that premise you'd have to pick...

(As an aside, `runtime.fileAttachments` isn't documented either.)

PoC: ~~~js function defaultFileInput({value, ...options} = {}) { const toFile = async attachment => new File( [await attachment.blob()], attachment.name, {type: attachment.mimeType} ); const setValue = async (input, value) => {...

Not sure how applicable it is here, but in other cases I've used thenables as lazy promises that only evaluate when they are being resolved.

> I suppose it might be okay to check if input.files has been set before setting it, and if so ignore the initial value Yes, a dirty flag should suffice...

Among the per-column options that may be added in the near future are: - data acessor for derived columns (https://github.com/observablehq/inputs/issues/83) - comparator to sort complex values (https://github.com/observablehq/inputs/issues/84) - header formatter...