Skip to content
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

Support remote includes #731

Open
apupier opened this issue Jun 20, 2023 · 3 comments · May be fixed by #737
Open

Support remote includes #731

apupier opened this issue Jun 20, 2023 · 3 comments · May be fixed by #737
Labels
💬 discussion Disccussion on new features, projects, etc... ✨ enhancement

Comments

@apupier
Copy link
Member

apupier commented Jun 20, 2023

Currently remote includes are not resolved (neither in the preview, neither in completion of attributes)

https://docs.asciidoctor.org/asciidoc/latest/directives/include-uri/#reference-include-content-by-uri

example:

include::https://gist.githubusercontent.com/apupier/528a635931932adbdf755303e0116314/raw/f55d188f903ede2a9f3a25c7deeb28046810fe5c/test-remote-attribute.adoc[]

== test

{remote-test}

preview gives:
image

@apupier apupier added ✨ enhancement 💬 discussion Disccussion on new features, projects, etc... labels Jun 20, 2023
@ggrossetie
Copy link
Member

Did you try with :allow-uri-read:?

@apupier
Copy link
Member Author

apupier commented Jun 22, 2023

image

@ggrossetie
Copy link
Member

setting the allow-uri-read attribute securely from the CLI or API

You need to enable this feature by setting allow-uri-read in your settings (or in your .asciidoctorconfig):

{
    "asciidoc.preview.asciidoctorAttributes": {
        "allow-uri-read": "",
    }
}

Having said that, it does not seems to work inside VS code:

image

apupier added a commit to apupier/asciidoctor-vscode that referenced this issue Jun 29, 2023
from what i understood, placing the allow-uri-read in attributes should
have done the thing but it is not working... to investigate

resolves asciidoctor#731

Signed-off-by: Aurélien Pupier <[email protected]>
@apupier apupier linked a pull request Jun 29, 2023 that will close this issue
apupier added a commit to apupier/asciidoctor-vscode that referenced this issue Jun 30, 2023
apupier added a commit to apupier/asciidoctor-vscode that referenced this issue Jun 30, 2023
apupier added a commit to apupier/asciidoctor-vscode that referenced this issue Jun 30, 2023
apupier added a commit to apupier/asciidoctor-vscode that referenced this issue Jul 4, 2023
ggrossetie pushed a commit that referenced this issue Jul 4, 2023
part of #731

Signed-off-by: Aurélien Pupier <[email protected]>
apupier added a commit to apupier/unxhr that referenced this issue Aug 8, 2023
it avoids to rely on `process.execPath` which resolves to `code` binary
in VS Code context although it expects the `node` binary

relates to asciidoctor/asciidoctor-vscode#731

Signed-off-by: Aurélien Pupier <[email protected]>
apupier added a commit to apupier/unxhr that referenced this issue Aug 17, 2023
especially targeting VS Code

fixes ggrossetie#98
relates to asciidoctor/asciidoctor-vscode#731

Signed-off-by: Aurélien Pupier <[email protected]>
apupier added a commit to apupier/unxhr that referenced this issue Aug 17, 2023
especially targeting VS Code

fixes ggrossetie#98
relates to asciidoctor/asciidoctor-vscode#731

Signed-off-by: Aurélien Pupier <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💬 discussion Disccussion on new features, projects, etc... ✨ enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants