Yoshiya Hinosawa
Yoshiya Hinosawa
@mmuddasani @bjesuiter Thanks for considering jsonc support with retained comments. > Microsoft's jsonc module that @farsightsoftware found appears incredibly comprehensive. Someone has even ported it as a third-party Deno module:...
> do you agree with "importing" this lib into deno std or do you simply propose usage of this lib? Because we have `npm:` specifier now, we recommend using `npm:comment-json`...
Core team is not in favor of exposing jsonc related features as Deno CLI feature. I think using Rust is not an option for this issue.
Though we are open to new type improvement suggestions to `std/collections`, I'm closing this one as there's no particular action is possible about this for now
If the user want to skip some specific kinds of error, then they can wrap the original function like the below: ```js await retry(async () => { try { return...
I'm personally open to the Path class idea. There was also past discussions (though it's rejected in them): - https://github.com/denoland/deno_std/issues/2072 - https://github.com/denoland/deno_std/issues/678 There's also a PR to implement [dax](https://github.com/dsherret/dax)-inspired Path...
> as long as we kept the API simple and inspired mainly by the [URL](https://developer.mozilla.org/en-US/docs/Web/API/URL) interface, which I like. hmm, that sounds very limited compared to the dax-inspired Path class...
We use `@actions/tool-cache` for extracting zip and it depends on `unzip` in PATH. (They seem to have moved to system's `unzip` intentionally https://github.com/actions/toolkit/blob/main/packages/tool-cache/RELEASES.md#112) I think this is by design. cc...
Looks these are all done now. Thanks for your efforts!