Breaking change in readme file format?

Describe the bug On MacOS, I was trying to generate a Python SDK. The README files for Python tend to use the variable python-sdks-folder and explicitly ask you to set that when generating.

However, when I supply this, autorest ignores it and generated my code in the ./generated folder instead of what I specified.

If I use --version:3.0.6337 then autorest picks up the value and generates the code in the correct location.

Expected behavior I would expect this argument to be picked up by autorest and honored.

Additional Context Versions

   Loading AutoRest core      '/Users/travisprescott/.autorest/@autorest_core@3.0.6337/node_modules/@autorest/core/dist' (3.0.6337)
   Loading AutoRest extension '@microsoft.azure/autorest.python' (~3.0.56->3.0.62)
   Loading AutoRest extension '@microsoft.azure/autorest.modeler' (2.3.44->2.3.44)

[timotheeguerin]

@tjprescott This was a regression between the integration of m4 and the python generator since version 5.0.0-preview.4

Made a PR on the python repo to fix it for new versions https://github.com/Azure/autorest.python/pull/897

I kept this issue open so we can see if we can have a better solution than this. I think the best solution is to load all nested configs that are part of the plugin name splitted by /

so for plugin python/m2r it would try to load nested config under

• python
• python/m2r(Don’t really see anybody ever using that)

[tjprescott]

Thanks @timotheeguerin!