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 has been archived by the owner on Aug 28, 2024. It is now read-only.
I want to extend a portion of the library. In my file that I'm using to test it I do require_relative '../ruby-nessus/lib/nessus.rb'
However, internal to the lib/ directory everything uses require. So my script does a 'relative require' which loads files that do a regular 'require', which is using the installed gem (this is my best understanding of what's actually happening). Short of creating a gem and installing it every time I make a change, what is the best way of handing this?
The text was updated successfully, but these errors were encountered:
I think it's not a good pratices to extend the library with a require relative.
I recommand to use a Gemfile and bundle to require the gem in a other project.
(I don't know what best practice is here.)
I want to extend a portion of the library. In my file that I'm using to test it I do
require_relative '../ruby-nessus/lib/nessus.rb'
However, internal to the
lib/
directory everything usesrequire
. So my script does a 'relative require' which loads files that do a regular 'require', which is using the installed gem (this is my best understanding of what's actually happening). Short of creating a gem and installing it every time I make a change, what is the best way of handing this?The text was updated successfully, but these errors were encountered: