I like this approach more because I can scan the code that renders the Box component and easily spot that it takes two children. If the Box took any props, they'd be within the opening <Box> tag, and they would be distinct from any children props.

a strategy game for me is mostly about the mechanics and the replayability. I love good art and design, but function follow form!

Almost always form objects wrap existing model or two.

An additional usecase is where we would like to update multiple records

Some developers found work arounds by using virtual attributes to # skip validators

I have developed a simple pattern that copies errors from the model or the service into the form object so that the view can still use those errors

Yes, i'm trying to find the union of two relations

Ok, fixed it by upgrading docker

Knowing exactly what happens in your application can mean the difference between feeling in full control or experiencing deep frustration. Personally, unknowns drive me crazy, which in turn often leads to all sorts of experiments and/or debug sessions.

The CSS Zen Garden era was hugely inspirational to many.

Repeatedly posting in this thread that there are problems, won’t actually get anything fixed.

I’m fan of maps (in real life and in games), and the map play here is interesting

Don't you hate to repeat yourself? For example, I hate working on anything related to user authentication or authorization that isn't directly related to the system I'm working on. I see it as necessary evil, an accidental complexity.

To be honest, I'm not sure what networking activity docker-compose is doing directly vs. what the docker daemon is doing.

It looks like your links for "this" and "that" no longer work, and I'd be really curious to see.