You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rather than using the Importer Marker in file to check whether the target file / marker name / line range is correct or not, Importer should be able to add a support for imperatively running a single command to check the validity.
For example, with YAML definition of
# == import: some-data / begin from: ../../../some/dir/file.yaml#[some-marker] ==# == import: some-data / end ==
The target file may be incorrect, and you'd only know when you run importer update.
Instead, Importer can add importer get and run it something like
importer get ' ../../../some/dir/file.yaml#[some-marker]'
The text was updated successfully, but these errors were encountered:
🔮 Relevant Command
New command
🗂 Language Type
All
🔎 Request Details
Rather than using the Importer Marker in file to check whether the target file / marker name / line range is correct or not, Importer should be able to add a support for imperatively running a single command to check the validity.
For example, with YAML definition of
The target file may be incorrect, and you'd only know when you run
importer update
.Instead, Importer can add
importer get
and run it something likeimporter get ' ../../../some/dir/file.yaml#[some-marker]'
The text was updated successfully, but these errors were encountered: