Feature/expose export filename #282
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add Scorecard workflow for supply-chain security
Updated the SECURITY.md file to focus on reporting security issues and removed sections about supported versions and reporting vulnerabilities.
Revise SECURITY.md for security issue reporting
Introduces a new Sponsors section in the README, highlighting Lefebvre as a Bronze Sponsor and displaying their logo. Adds the sponsor-lefebvre.png asset to the repository.
Add new sponsor forml
chore: version packages
|
@optimalcharb is attempting to deploy a commit to the OpenBook Team on Vercel. A member of the Team first needs to authorize it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I saw #278 and thought it would be a simple fix by exposing defaultFileName to PDFViewerConfig.plugins. Correct me if I'm wrong. Also it's just three lines so you could consider adding it to your next update instead of merging a PR.
Correcting PR #281, still not sure if I am proposing merge to the right branch