fix: Get the sharing token the new way #92
Merged
+4
−2
Conversation
This file contains 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
NC 31 does not provide the sahring token in an invisible HTML element anymore. This fixes this issue by using the path of the richdocuments plugin here: https://github.com/nextcloud/richdocuments/pull/4030/files This refers to jgraph#90
janLo
force-pushed
the
fix-issue-90-sharingToken
branch
from
b97a17a to
bd3ec8f
Compare
|
Not reviewed, nextcloud integration doesn't fall under our SOC 2. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
NC 31 does not provide the sharing token in an invisible HTML element anymore. This fixes this issue by using the path of the richdocuments plugin here:
https://github.com/nextcloud/richdocuments/pull/4030/files
This refers to #90
I have not tested the change because I have no setup to compile the minified JS here!