hey, what would be a good way to validate/coerce/enforce constraints on data going into datascript

like, i want some attribute to always be a float, for example

ideally you'd have functions a level higher than transact! validating the inputs. Otherwise you can have your own transact! which takes a schema (or is called with an implicit schema) that the validations are run against.

mmk

so why would you suggest something higher level than a custom transact!?

maybe i need a defmulti...

well, it depends on where you want your validation logic

if you're ok on having static validation in database schema

then custom transact! is good

kk

so i have something that looks loosely like this

(defc foo "")

(input
  :value foo
  :input (if-let [n (parse-number @%)] (reset! foo n)))

i’m trying to stop values i don’t like

but if someone writes 42a

foo is not reset, so :value does not update

it's usually a good rule not to mess with what user inputs

highly frustrating

you don’t even know what i’m doing...

only numbers are OK for this input

only judge by the example

well i want to accept numbers in the field but not letters

if i get it working, i’ll add errors and stuff to make it obvious what is going on

my suggestion still stands 😉 but doesn't it work that way already?

starting with the basics

no, it doesn’t work that way

:value only does something if the cell changes

personally I strongly dislike inputs that do not show what I typed in

kind of irrelevant

in this case it seems you have to have two cells

oh?

oh, it seems that I've not understood you from the start, sorry

do you actually want to show whatever user inputs, but only store the valid input in the cell?

either is fine

i only want to store valid input

but if you don’t store it, it will just disappear on page refresh

it will silently die

then you have 'user input'/'user input error'/'valid parsed value' pieces of data

that you need to store

yeah

hangong, i’m going to restart slack

it’s freaking

like..

(defc foo "")
(defc foo-raw "")

(input
  :value foo
  :data-error (cell= (= foo foo-raw)
  :input (do  (if-let [n (parse-number @%)] (reset! foo n))
              (reset! foo-raw @%)))

:value foo-raw, no?

well.. no

i mean, it doesn’t matter

it’s beside the point

because the user can write whatever they want in the field and :value gets stale the moment something doesn’t validate

it’s either not representing what is actually being used for calculations elsewhere, because it’s not showing the valid bit

or it is showing what will be used for calculations when you load up the page, but you might lose some (invalid) input

yeah, storing invalid input is too much I think

it’s like...

i’m using cells to make the app more responsive, no need to submit forms and wait for a page refresh

but now i’m not sure what to do, show calculations that don’t line up with input, or restrict input, or… something else??

that's what I was trying to suggest

part of the answer to that question

UX rule #1: don't mess with user input

but it’s just not possible

which means showing whatever user typed in, highlighting errors and running calculations only when the error is cleared

hmm

spreadsheets don’t do that (for example)

you can have an action appear beside the error to "sanitize input"

spreadsheets propagate #ERROR

yeah

so you can do that too

dependening on who is your user

one model might be better than the other

(e.g. if your users are heavy spreadsheet users, spreadsheet model makes more sense)

ok so um

that’s a good question

actually

hmm

i think i need to sleep on this

:value is giving me so much grief, lol

@jumblerg: wow, i was extending the clj castra writer to convert joda-time to instant just last week!

@onetom: good to know i’m not the only one. you can use it as follows:

(defn remote [endpoint & [opts]]
  (let [opts* {:url url :on-error #(when dev (println  %)) :reader-opts {:handlers {"r" identity}}}]
    (c/mkremote endpoint q/session q/error q/loading (merge opts* opts))))

hi anyone know where the hoplon jquery-selectize repo ended up?

@raywillig: here maybe? https://github.com/cljsjs/packages/tree/master/selectize

unless you’re looking for a hoplon specific version

@jumblerg: thx that’s just the ext file. i grabbed the jar from clojars. I just needed to look at the source

yeah, there’s a hoplon defelem that @alandipert or @micha whipped up a while back

@raywillig: you can view the files in the jar with vi or emacs, i think both know how to do that out of the box

wow, didn’t know that. very coo

l

in emacs at least you can edit jars in place also, which is handy/dangerous

but i do it on the reg

handgerous

hi all, is there a special hoplon form for websocket