Breaking Down Oxfmt: --stdin-filepath Does Not Respect

When using --stdin-filepath, ignorePatterns from .oxfmtrc.json doesn’t kick in - file content still flows through, no filtering. This mirrors #17729’s fix in #17732, where this flaw caused unformatted code to pass through. Here’s what’s really happening: oxfmt treats the file path as a fixed input, bypassing the ignorePatterns check. Even a single line matching ignored/** won’t halt output. This matters because tools like jj, which format code in pipeline mode, expect --stdin-filepath to respect ignore rules. Without that, ignored files get processed - damaging consistency. The fix appears in CLI positional args but not in stdin routes. For developers, this means ignored files can leak into formatted output if not properly routed. Bucket Brigades: The formatter runs - no warning, no block. But the oversight risks cluttered, unintended code in results. Do map ignored paths carefully. Never assume --stdin-filepath ignores patterns by default - verify your config. Closes in 120 words. This behavior affects how developers package and share code safely.nnIs your ignored file sneaking into formatted output? Check your .oxfmtrc.json path rules. When ignorePatterns fail to block file paths, formatting tools miss the mark - precisely what happened with jj and prettier. Protect your pipeline’s integrity by enforcing pattern consistency. The bottom line: Respect file path patterns or risk bypassing your entire formatting workflow.nnDoes this mismatch confuse your CLI setup? It does - especially if you rely on jj or prettier in --stdin-filepath mode. The fix is clear: format standard paths correctly, or let ignored files slip through.nnoxfmt’s stdin path behavior reveals a silent gap - one developers must fill to keep formatted output clean and intentional. The fix exists, but only if you’re explicit about ignoring patterns in file input, not just CLI flags.