@skillstopractice agreed!

@skillstopractice I guess?? But each time we try, we think oh yeah, selects are still hard

Thank heavens it's Thriday*

* our company is a 4 day week company, so Thursday is our last working day of the week.

@skillstopractice Well, just "the next thing" that'll need replacing!

We use React on a few pages (most of the app is normal Rails / Turbo, after a big effort to strip out everything else) so we use react-select. The main reason we can't strip that out, just like that, is that it has a "createable" hook. And it works fine in React and Rails and test land. https://react-select.com/home It'll need to go at some point, but it's OK for now. What do you use?

bye, jQuery and select2! (actually merging this time...!)

@HansTenner Sadly whilst I also use LibreOffice for the good reasons you mention, I find its UI and UX grating. But I, also, am not in a position to contribute, so I should just shut up.

@HansTenner are you just saying that for the sticker?

@neonbubble such a clue, when the ticket includes the clause "all we want to do is just..."

@baldur Safari has been the new IE9 a few times of late.

@Daojoan cc https://justsimply.dev

@zmanguy yeah, this is my pre-TDD, pre-having thought about the right approach at all, approach. TDD is too heavy at this very early stage, for me anyway, and I like to see the thing working in the browser for my brain to decide if it's the right direction or not.

I invented* a thing. Instead of trying to get the migration right from the start, on this spike branch I've added methods in the model that respond in the same way a call to the attribute on the table would respond. Then I don't need to create an unholy amount of up-down migrations whilst I'm still noodling.

(Oh, yeah -- AI here stands for Advance Information sheet. Don't worry!)

* of course, this will be how everyone does it and I've just never noticed.

@rgarner bad news

@rgarner 😏😖🤪