Make Options a required constructor argument of Store#1309
Conversation
This decouples RDoc::Store from RDoc::RDoc, which is only used to access RDoc::Options.
Deploying rdoc with
|
| Latest commit: |
a68dfb5
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d49372c5.rdoc-6cd.pages.dev |
| Branch Preview URL: | https://decouple-store-and-rdoc.rdoc-6cd.pages.dev |
|
@kou Updated 👍 |
Co-authored-by: Sutou Kouhei <kou@clear-code.com>
|
Hello, again! 👋 This is a breaking change for SDoc. As part of a performance optimization for its test suite, SDoc manually constructs fresh
|
|
It's unfortunate that it added additional effort to upgrade, but I don't consider |
|
I ran into an issue with this change as well. I was using RDoc to parse documentation for an rspec matcher. I'm not sure if I am using it correctly, maybe I can get some guidance? I'm doing something like this now: |
Since
Storerelies on accessingOptionsfor various tasks, it should simply hold a reference to theOptionsobject itself, instead of accessing it through anRDocinstance and forming an unnecessary coupling.This PR requires
Storeto be initialized with anOptionsinstance.