What happens if we import code from an existing plugin into an Mkdocs-Macros module?

[fralau]

Originally started as an issue on the relevant plugin's website (#timvink/mkdocs-table-reader-plugin/57). Please consult this issue for the follow-up.

To get an idea of how this idea could work in practice, I tried the experiment of writing a module that would import the applicable code of mkdocs-table-reader-plugin. It was very straightforward.

Here is the minimal code for a module (main.py in the root directory of the MkDocs project):

from mkdocs_table_reader_plugin.readers import *

def define_env(env):
    """
    This is the hook for the functions (new form)
    """
    for reader in READERS.values():
        env.macro(reader)

It does the following: it lists all the readers, which are conveniently listed in READERS (['read_csv', 'read_table', 'read_fwf', 'read_excel', 'read_yaml', 'read_json', 'read_feather', 'read_raw']) and declares them as macros. And voilà they were imported as macros available in every markdown page! Now its even possible to add programming logic (for repetitive actions), etc..

I attached the whole Mkdocs test project (mkdocs-tables-module.zip), so that you could reproduce my experiment, if you wish. It only requires a pip-install mkdocs-macros-plugin.

I just wished to know what you think about it, and if there could be potentially workable ideas there?