Alexandre Morgaut

The dynamic import standard is in stage 3 It is now supported by chrome

@chicoxyzzy yes :-) I limited my mention to Chrome which shares v8 with node few related resources: - https://techsparx.com/nodejs/esnext/dynamic-import.html - https://github.com/nodejs/node/issues/24894

+1 for Nashorn & Rhino we have an Android project in which we embed rhino

> I think you want `explode: true` for that parameter: https://spec.openapis.org/oas/v3.1.0#fixed-fields-9 it doesn't resolve this issue ⚠️❌ the specification doesn't say how to serialize the object

Use Case: I have the same issue regarding a back-for-frontend which host many independant services, all with their own versionning and ownership, then defined in many separated Open API files...

As a Green IT evangelist, I would say > "such implementation is great" > "please fail early and interrupt useless transfert and process costs" As a JS developper, I would...

Moving to v1.0 is clearly a big step :-) As it is a major version, breaking some legacy API compatibility is technically allowed by semver but does it worth giving...

I confirm the initial regexp doesn't validate many international emails I extracted those ones from wikipedia for testing - https://en.wikipedia.org/wiki/Email_address - https://en.wikipedia.org/wiki/International_email ``` [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]...

Thanks for the link > My recommendation is not to rely on formats to validate emails, (...) and do the actual validation in the application, to the level that is...

> It may be possible to add Hermes to the list on [test262.report](https://test262.report) as well? that would be great!