fiddly | Create beautiful and simple HTML pages

I have a data table as follows

In SQL it is very easy to apply different aggregate functions to different columns, e.g. :

Just wondering if anyone knows of the best way to upgrade a JSON structure Deserialisation to a new class type.

To further explain the legacy value was

I am after the best practice for handling incomplete stripe connected account onboarding.

When onboarding goes smoothly, everything is simple. But there are fiddly edgecases everywhere, which results in a lot of permutations of values for account requirements

These include

• current_deadline
• currently_due
• disabled_reason
• errors
• eventually_due
• past_due
• pending_verification

This creates a lot of complexity.

I need a simple way to:

1. figure out if the connected user needs to be notified of something (i.e. that they need to give more info), and
2. what to tell them.

My current strategy is to check if errors is empty, and if not, simply display them along with a link to manage the user's stripe account so they can address the errors.

But I'm worried this strategy will miss things (perhaps minor things that could be addressed before they become errors).

TL;DR I suspect most users will onboard without any problem, but for the few who do have issues, I want to ensure the app notifies them that they need to address them. What is the best way to do this? (using the information in requirements or other info)

This is a bit fiddly, but I'll try to explain it. What I'm trying to get working with CSS is:

1. Two divs at the top of the page ("A" and "B"), side-by-side with a fixed width of combined 400px (if the window is too narrow to see both, then a scrollbar should appear, I do NOT want one div jumping beneath the other)
2. Those two divs can be of different heights, though - sometimes div A will be higher, sometimes div B.
3. I want some long text to appear directly beneath div A. If div B is higher than div A, then the text should flow around div B.
4. The text should display no wider than 400px, but if the window is narrower, then it should display as narrowly as needed. The text should be no wider than the viewport.

So to summarize, I want the two side-by-side divs on top to display the same way regardless of how narrow the window width is, but the text below div A to be responsive to the window width (and also not to overlap div B, if div B drops down further than div A).

Here's some code that isn't the right approach, but shows partly what I'm going for:

I am attempting to pass a collection of JNA structures to a native method but it's proving very fiddly:

Let's say we have a structure:

This is starting to bug me: In plotly express when using animation_frame, I know it's important to set ranges so data can be displayed consistently, otherwise data may vanish across frames. But for a column with categorical values (say 'US', 'Russia', 'Germany'), I cannot find any way to avoid disappearing data when not every frame contains all categories if I want that column to appear with different colors (in the code below, that column would be 'AnotherColumn'). Plotly documentation points out

Animations are designed to work well when each row of input is present across all animation frames, and when categorical values mapped to symbol, color and facet are constant across frames. Animations may be misleading or inconsistent if these constraints are not met.

but while I can easily set a range_color when I have a continuous color range, nothing of the sort seems to work for categorical data. I can somewhat workaround this by making my data numerical (e.g. 'US'-> 1, 'Russia' -> 2) bu that is both fiddly and the result visually unappealing.

If I want to open a workspace on a regular local folder under C:\ I can just execute the command:

I was originally looking to (manually) write a simple tokenise/parser for my grammar, but one of my requirements means that tokenising is a bit fiddly.

I need to be able to support the notion of delimited strings where the delimiter could be any char. eg. strings are most likely to be delimited using double quotes (eg. "hello") but it could just as easily be /hello/ or ,hello, or pathologically xhellox

So, I started looking at what alternatives there might be to do a combined tokenise/parse... which is when I stumbled across petit parser.

Just curious whether this type of delimited string might be something that would be able to be parsed using Petit Parser? Thanks.