Feat: allow extract addon folder inside subdir of git repo

[zhuoqun-chen]

Scenario:

Assuming I'm developing an extension called dummy_addon and I have a github repo for it, the actual addon with blender_manifest.toml actually lives one level deeper.

dummy_addon
├── README.md
├── dummy_addon
│   ├── __init__.py
│   ├── blender_manifest.toml
│   ├── packageA
│   └── packageB
└── tests

Current extension can only recognize the structure where the project root has a blender_manifest.toml and my commit will allow the user to create a symlink that points to the actual addon package folder, which can be more convenient. This also works inside multi-root workspace where many add-ons are developed together.

[Mateusz-Grzelinski]

Just a quick reply,
Are you sure this is not done by setting blender.addonFolders?

Unfortunately I will not be able to review it in following week's.

edit: or are you trying to resolve blender.addonFolders automatically?

[zhuoqun-chen]

Hi @Mateusz-Grzelinski, yes, I'm trying to auto-resolve the actual addon folder.

However, after some investigation and your suggested blender.addonFolders, it seems that two functions under addon_folder.js:

async function tryFindActualAddonFolder(root) {
    if (await folderContainsAddonEntry(root))
        return root;
    for (let folder of await (0, utils_1.getSubfolders)(root)) {
        if (await folderContainsAddonEntry(folder)) {
            return folder;
        }
    }
    return Promise.reject(new Error('cannot find actual addon code, please set the path in the settings'));
}

async function folderContainsAddonEntry(folderPath) {
    let manifestPath = path.join(folderPath, "blender_manifest.toml");
    if (await (0, utils_1.pathExists)(manifestPath)) {
        return true;
    }
    let initPath = path.join(folderPath, '__init__.py');
    try {
        let content = await (0, utils_1.readTextFile)(initPath);
        return content.includes('bl_info');
    }
    catch {
        return false;
    }
}

alreay does the job. I made the commit because I had some trouble as described in #191, and this commit + pin dependency can fix this.

Now I can't reproduce my problem either. So maybe I can close it for now. Thanks for the info!