feat(tangle): add report_on_empty option in core.tangle

[pysan3]

Do we need this warning?

neorg/lua/neorg/modules/core/tangle/module.lua

Line 424 in aa8e66d

utils.notify("Nothing to tangle!", vim.log.levels.WARN)

I run an autocmd for all norg files to automatically try tangling, and I don't want to get a warning everytime.

@pysan3

Changes

• Add report_on_empty option.

module.config.public = {
    -- Notify when there is nothing to tangle (INFO) or when the content is empty (WARN).
    report_on_empty = true,
}

• Fixes some type errors from refactor(luacheck): workaround lua type check #1162

Notes

• I'm not sure how to update the wiki: https://github.com/nvim-neorg/neorg/wiki/Tangling
  • I'd be happy if you could guide me how.
• Possibly conflicts with feat: allow upward paths in tangle #1167

[vhyrro]

I sure love github's default commit messages. Either way the conflict should be resolved now properly. Could you double check if this is the case @pysan3? Afterwards we can merge it.

[pysan3]

@vhyrro As you can see, now the ci result is a ❌ due to these errors caused by the PR I mentioned.

Are they gonna be my fault now? Should I fix them in this PR?

[pysan3]

Doing some experiments, does the current v1 parser parse relative tags correctly in the first place?

I don't think this exports to the correct path (or doesn't do tangling in the first place?).

#tangle ../init.lua
@code lua
print("Hello world")
@end

Upward relative path does work when specified in the @document.meta tho.

[pysan3]

The above commit resolves the conflict and uses better mechanism to generate the output filepath without some complicated lua code like counting gmatch.

[vhyrro]

Fantastic, thanks a lot for all the work.