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
This would help for additions and modifications that developers find useful for their own workflow, as well as make it easier to work on this repo
A proposal would be to include a skeleton directory containing stubs corresponding to files in dragon/:
contrib/
args.rb
assert.rb
console.rb
(...)
And have the runtime a) hotload those files in development, loaded before game files, b) compile them in similar order on top of the baked-in contrib code.
Symlinking $dr_root/contrib/some_file.rb to a checkout outside of the directory could also work.
Example use case
#91 was extracted from a real-world override placed in app/lib/console.rb:
But I found myself missing the override in other projects.
In order to share it, I'd have to symlink or copy it to each project, and add the require line to my code.
Together those bring enough impedence that I haven't done it for the smallest projects, but those stand to gain equally, if not moreso due to auto-inclusion being more powerful for rapid prototypes.
This would help for additions and modifications that developers find useful for their own workflow, as well as make it easier to work on this repo
A proposal would be to include a skeleton directory containing stubs corresponding to files in dragon/:
And have the runtime a) hotload those files in development, loaded before game files, b) compile them in similar order on top of the baked-in contrib code.
Symlinking $dr_root/contrib/some_file.rb to a checkout outside of the directory could also work.
Example use case
#91 was extracted from a real-world override placed in app/lib/console.rb:
Expand
But I found myself missing the override in other projects.
In order to share it, I'd have to symlink or copy it to each project, and add the require line to my code.
Together those bring enough impedence that I haven't done it for the smallest projects, but those stand to gain equally, if not moreso due to auto-inclusion being more powerful for rapid prototypes.
Related to #52
A reframing or extension of this could be a solution for Amir and Levi's config enhancement, discussed here: #52 (comment)
For example, all rb files under $dr_root/autoload could automatically required.
With a stub named config.rb showing some common overrides.
Thanks
The text was updated successfully, but these errors were encountered: