Paul Bakker

(re)marked this as Draft again, as I'm contemplating some additional changes, but would already appreciate some feedback on the general direction of extracting the results into their own json files....

Any feedback anyone? Don't want to spend more time on this if the general direction of this PR, namely splitting the tests and results into separate files, is gonna be...

I guess the change in where the test results are stored would break [the mechanism in Babel that downloads and converts the compat data](https://github.com/babel/babel/blob/c446ff85c28e117ebf3cd72cd34ef358f1077aa8/packages/babel-compat-data/scripts/utils-build-data.js), but imho it would be easy...

@ljharb @chicoxyzzy any chance to get some feedback on the general idea to extract the results out from the data-*.js files and into .json files? Is it worth my time...

Ok, but what does that mean exactly? 🙂 Does it mean you and/or others are actively thinking about whether or not this change is something you're willing to accept? Or...

@ljharb how's the thinking going?

@chicoxyzzy @ljharb sorry to nag again, but would really like to move on this... So how about it? Will you support a change in the proposed direction?

Great! So @chicoxyzzy what do you say?

Or consider contributing an implementation to Rhino itself: https://github.com/mozilla/rhino/issues/948, https://github.com/mozilla/rhino/issues/949

Same usecase here: you'd want consumers of web components not having to know the details of how the web component was implemented, but just do what they normally do and...