Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Allow the user to configure the safe mode

See original GitHub issue

I think we should allow the user to configure the safe mode: https://asciidoctor.org/docs/user-manual/#running-asciidoctor-securely

Currently the value is unsafe according to the value printed when using the attribute {safe-mode-name} in a document.

{safe-mode-name}

AsciiDoc Plugin Version: 0.30.7

IntelliJ IDEA 2019.2.3 (Ultimate Edition)
Build #IU-192.6817.14, built on September 24, 2019
Runtime version: 11.0.4+10-b304.69 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.15.0-58-generic
GC: ParNew, ConcurrentMarkSweep
Memory: 1981M
Cores: 8
Registry: 
Non-Bundled Plugins: Batch Scripts Support, CMD Support, CheckStyle-IDEA, FindBugs-IDEA, JFormDesigner, PsiViewer, org.asciidoctor.intellij.asciidoc, org.jetbrains.idea.grammar, org.jetbrains.plugins.slim, BashSupport, com.dmarcotte.handlebars, com.jetbrains.lang.ejs, com.jetbrains.plugins.jade, com.wix.eslint, org.intellij.scala, org.jetbrains.plugins.ruby

Issue Analytics

State:
Created 4 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

ahus1commented, Oct 16, 2019

A new pre-release 0.30.10 of this plugin includes this feature. The preview is available from GitHub releases and the IntelliJ AsciiDoc EAP repository.

1reaction

ahus1commented, Oct 13, 2019

“unsafe” is the default when running Asciidoctor CLI from the command line. As in documentation-as-code environments developers would check out a repository and then build the docs locally, it is safe to assume that the “unsafe” mode from the command line is the right default.

Having said that the user should be able to configure this in the settings of the plugin.