-
-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
resolves #1507 introduce an in-memory cache (Node.js) #1523
base: main
Are you sure you want to change the base?
resolves #1507 introduce an in-memory cache (Node.js) #1523
Conversation
ea1863b
to
a59b15d
Compare
This pull request provides a custom implement of This pull requests also introduces an API to interact with the cache: Asciidoctor.Cache.enable()
Asciidoctor.Cache.disable()
Asciidoctor.Cache.setMax(500)
Asciidoctor.Cache.reset() |
a59b15d
to
b7c1940
Compare
b7c1940
to
a938a6a
Compare
a938a6a
to
aba02c0
Compare
def require_library name, gem_name = true, on_failure = :abort | ||
if name == 'open-uri/cached' | ||
`return Opal.Asciidoctor.Cache.enable()` | ||
end | ||
original_require_library name, gem_name, on_failure | ||
end |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mojavelinux I'm a bit concerned about this hack, could we find a better "hook" in Asciidoctor core?
Waiting for a change in Asciidoctor core to properly hook the in-memory cache. |
resolves #1507