Guillaume Giudicelli

ElementGwnerator and TransformGenerator

You’d have to stitch them together. Depending on what you want it might be easier to block restrict one element and use a transform (or a parsedNodeTransoform ? Any support...

> I haven't looked deeply into the code, but on every side of every hex you ought to check elem->neighbor_ptr(s), and if it's not null then do things like check...

I ll do it soon!

@lynnmunday note that because you edited my username into the previous comment, I never actually got a notification with that text

This is also relevant for examples. A number of examples are not tested, just orphan inputs in a module https://github.com/idaholab/moose/issues/26442

@dschwen was looking at multi-level includes (including Saline in FP, and running another module that builds with FP)

Let's squash these commits together a bit, especially the "update some file" commits. Where are we on the documentation failure with thermochimica? Do we still need all recipes to check...

The build is also failing because we are passing some strict flags from MOOSE (-Werror-unused etc) on Saline

> > The build is also failing because we are passing some strict flags from MOOSE (-Werror-unused etc) on Saline > > What a wonderful opportunity to fix the Saline...