AnirudhJindal

Hi @Julian, I'd like to work on adding UUIDs to test cases and individual tests. I've read through the discussion and understand the approach. **My Plan:** - Start with `enum.json`...

Hi @jdesrosiers, Thank you for the feedback! I understand I moved too quickly and should have waited for community consensus first. I'd like to create a proper proposal addressing the...

Hi @jdesrosiers, Thanks for the feedback! Since IDs need to be somewhat readable yet unique, I propose using a semi-readable structure combined with short UUIDs. Here's the idea: --- ###...

hi @jdesrosiers , my stance on the fundamental questions are as follows: **Question 1: What Needs an Identifier?** I think both test cases AND individual tests need them. your example...

**Question 1: Test Cases vs Tests - Both Need IDs** I think we absolutely need both levels of IDs, and the numbers from the actual test suite prove why this...

> I disagree. It is far from normal and highly discouraged for an implementation to skip entire features. One or two tests cases (like the file: URI scheme example) or...

Hi @jdesrosiers, I’d like to move forward with Option 2 for now — using a simple MD5 hash of { schema, data, valid } to generate test IDs. This approach...

Hi @jdesrosiers, > > > > So, the id-checking script should generate the id from the schema/data/valid fields, compare that id to the one in the test, and report if...

Hey @jdesrosiers, Really sorry for the radio silence! I'm currently drowning in university exams and intern interview prep, so it's been a bit chaotic over here. I'll need a couple...

Hey @jdesrosiers, I’ve updated add-test-ids.js to incorporate the defensive programming points you mentioned. Some of the earlier checks came from initially making it work for a single file, so I’ve...