Simone Carletti

Thanks for the feedback. Yes, we integrated OpenAPI and one of the goal was to be able to take advantage of the various tools built around the specs. I don't...

> Do you happen to have a 2.0 spec or the Swagger 2.0 file I could try with autorest or another generator library? Sadly not. We went directly with v3.

The reason why the path includes 1.9.1 is because Ruby core decide to not change the rubygems path. So far, it just happens with this Gem, but I didn't have...

@aeden I'm removing myself from review. This field was published almost unintentionally. We'll have to evaluate how to expose the various TLD settings, but we made some internal changes to...

Thanks @adamkittelson. If you feel like providing a patch, it will definitely speed up the chance to get the change merged. 😉

From this thread: https://github.com/nanoc/nanoc/issues/1545#issuecomment-886008483 > Ruby Sass indeed needs to be replaced in Nanoc, but I haven’t made much progress with it yet. sassc (and the associated [libsass](https://github.com/sass/libsass)) are also...

I agree. Is there a way to keep the legacy Zone.File around for the time being, and delegate to the new one (maybe with a warning)?

> Can I take this issue? Hi @sushant102004, if you want to submit a PR we will be happy to review it.

@unixcharles it took years, but I finally managed to rebase this PR to present and apply the fix I had in mind when I started. I also managed to include...

> Thanks @weppos, had forgot about this one 😃 Understandable, 2019 is a long time ago 😂 . Thanks for shipping it so quickly!