brandonlangley

@joshuahansel - I wonder if this is related to this discussion we had on Slack in October about a similar brace substitution situation. I have copied and pasted the conclusion...

@joshuahansel - > 1. Combine inputs without merging > 2. Substitute `${val}` > 3. Evaluate commands like `${fparse blah}` > 4. Merge within the combined input Just wanted to note...

@joshuahansel - > change the merge operation to preserve the order of the nodes in the root being merged in With your original example `app-opt -i fileA.i fileB.i`, I assume...

@joshuahansel - I took a stab at this and changed the merge logic so any block that exists in both inputs is moved to the end of its siblings. So...

@joshuahansel - After running all of the framework tests locally, I just saw I have nine tests failing after this update that passed previously. I believe six of these are...

@joshuahansel - For the `regular.2d_overlay/projection_needed_receiving` failure, I printed the input after both the old and new merges. For reference, here is the full command running that test showing all the...

@joshuahansel - After a lot of time spent testing many scenarios, I have concluded input order does affect the outcome in various cases. - - - - - I verified...

@dschwen - I don't have permission to check the box, but this task from your list is complete and was merged with https://github.com/idaholab/moose/pull/25305. - [x] Jump to source (for jump...

@dschwen - This task from your list was merged with #26797 and can marked as complete now. ## WASP - [x] Parsing of incomplete documents

Added this to the NEAMS LSP / Frontend project and pinging @lefebvrera here too.