IRC logs for #farmOS, 2023-03-11 (GMT)

2023-03-10
2023-03-12
TimeNickMessage
[03:08:27]<FarmerEd[m]>I agree the simple field makes sense, I guess from reading the link, I've asked a similar question before... I must be losing it! 😄
[03:17:44]<FarmerEd[m]>I was thinking maybe a module, even a contrib module in addition to the proposed field that can create a library of these conventions from within a farms instance of farmOS that can produce a written form of just the conventions used by that particular farm, even if each convention comes from a different repo.
[04:00:07]* monkeyflowerfarm has quit (Quit: You have been kicked for being idle)
[05:45:03]<mstenta[m]>That's a cool idea!
[05:55:25]<FarmerEd[m]>It's possibly just a slight adaption of an idea @walt had for an online help section.
[08:21:58]<mstenta[m]>farmOS 2.0.2 has been released! https://github.com/farmOS/farmOS/releases/tag/2.0.2 🎉
[08:22:15]<mstenta[m]>> Ok think I have my 2.0.1 working right now.....
[08:22:15]<mstenta[m]>Sorry Farmer Ed 😅
[12:30:21]<mstenta[m]>Three PRs for review - all culminating in the Birth quick form...
[12:30:22]<mstenta[m]>https://github.com/farmOS/farmOS/pull/654
[12:30:25]<mstenta[m]>https://github.com/farmOS/farmOS/pull/655
[12:30:30]<mstenta[m]>https://github.com/farmOS/farmOS/pull/656
[14:41:08]<gbathree[m]>hauling through some intense use of the farmOS 2.0 api, great work all it works really well. Lots of little improvements, like 😃 thank you for making `measure` in `quantities not only not an `enum` field, but now also leaving it optional! That's a lot of stuff I'd normally have to put kind of BSy answers in I can now skip! Anyway, great job mstenta especially but really everyone for all the contributions to make this all work
[14:41:30]<gbathree[m]>* in `quantities` not
[14:44:14]<mstenta[m]>actually i think measure probably should be an enum... 😅
[14:44:15]<mstenta[m]>although it should definitely be optional
[14:44:36]<mstenta[m]>there is a list of "allowed values" for it... hopefully the API is validating those (even if JSON Schema isn't listing them in `enum`, which it probably should)
[14:45:31]<mstenta[m]>glad everything's going smoothly for ya gbathree !!
[14:46:14]<mstenta[m]>you're one of the OG farmOS v1 API power users, so that means a lot 🚀
[14:48:57]<gbathree[m]>well it's great, either way! But we'll definitely have a list of fixes for the api, lots of stuff it claims that aren't quite accurate still (you mentioned one example). Hoping we can help specify and clean those up, so you have the shiniest most accurate api and schema outputs!
[14:49:23]<gbathree[m]>but even with little hiccups like that, it's awesome
[14:50:20]<mstenta[m]>yea let us know what you're finding! we can open bug reports and get them fixed
[14:50:43]<mstenta[m]>i know you're using jsonapi_schema module extensively, so i imagine a lot of them are in that
[14:51:00]<mstenta[m]>(i recall fixing some that Octavio found early on in that module)
[14:52:15]<symbioquine[m]>On a related topic, is there a formal definition of the behaviour for the JSON:API [query operators](https://github.com/drupal/drupal/blob/60c2916b172481d10b3f82045804fd4d44...) other than reading the source code/tests? i.e. I don't see where the docs say whether `STARTS_WITH` can be applied to a relationship or what is supposed to happen if you use the `BETWEEN` operator on a
[14:52:15]<symbioquine[m]>string value.
[14:53:24]<symbioquine[m]>Many of them are intuitive for the most part, but not all cases.
[14:58:59]<symbioquine[m]>Obviously, I've read https://www.drupal.org/docs/core-modules-and-themes/core-modules/jsonapi... but it doesn't treat each operator very thoroughly, just some of the cases.
[15:10:43]<mstenta[m]>You're already deeper than I've had to dig symbioquine