Chris Markiewicz

It should be possible to add a check over ignored filenames and see if they match any filename rules.

* Text file: What is the contents of the text file, and where should it be placed? * % RECOMMENDED: This would be a significant undertaking. We would need $\frac{present}{present...

This would require a custom JSON parser, which has the potential to be a huge bottleneck.

Here are the things that we permit for potential recording: https://github.com/bids-standard/bids-validator/blob/49b87424732dff84bec8f06db4c50404f0649cbb/src/types/issues.ts#L8-L19 * code: Primary code like `HED_ERROR` or `HED_WARNING` * subCode: Secondary code. Initially used to report the specific fields...

Speaking just for me, as I have not discussed this with @nellh or @rwblair... > `file` will remain as an `IssueFile`-type object (that type is apparently only used in a...

I think I'd be okay with changing `Issue.line` to be `number | string`. It's not unused, so we can't just change it to `string` without complication, but if HED has...

Should `character` also be `number | string`? Or, if these are ranges, should we do `number | [number, number]` and HED can use arrays instead of converting to strings?

`character` is currently unused in the BIDS validator, but yes, the idea was character index, I think. I agree it's not terribly useful. For TSV, I think row+column makes more...

Is this an issue in the current (schema) validator?

@ericearl My understanding is that this needs to be resolved in the specification (and schema). https://github.com/bids-standard/bids-specification/issues/914 is where this needs to be finalized. My reading is that we came to...