You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 8, 2024. It is now read-only.
The whole hooks template and especially the Ruby hooks are in a somewhat hard-to-resolve state: apiaryio/dredd#917 I've written 5 lines of Ruby in my whole life and putting the template and the Ruby hooks into shape feels overwhelming to me. I'd like to port dredd-hooks-template to Node.js instead of using Ruby.
Why?
Because I'm able to maintain it in that case and to give it a full support, as well as anyone else in the company or new hires or Dredd contributors, as Dredd itself is in JavaScript.
Second, if the test suite itself is in Ruby, it brings Ruby dependencies to all of the other projects. That's an issue for Ruby hooks, where it constraints Ruby hooks' own dependencies, and it also feels strange (read as "makes CI setup complicated") in projects like Go, Rust, Python, etc. Unlike Ruby, thanks to web development, today Node.js is a common "buddy" of other languages, living alongside other-language projects, and people are used to work with it. Even hardcore backend Python people know how to npm install things.
If you don't know what I mean by the "buddy" thing, see e.g. this:
The Node.js hooks are a native part of Dredd, so there can never be a collision like Ruby hooks / Ruby hooks template dependencies. Node.js is mutually exclusive to additional languages supported by Dredd.