Paul Michalik

In connection with AWS SAM this is even worse. If you set for example your directories for temporary and binary directories, or the language version on global level via `Directory.build.props`...

I would support that. Currently, if you are using [`sam build`](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-cli-command-reference-sam-build.html) I have not found a way to provide alternative parameters such as temporary folder location or optimization flags to...

@chrisoverzero No, it does not. Trying with v1.55, it happily ignores the "aws-lambda-tools-defaults.json" in the project directory or in the global solution directory, no matter where I put it.

Hm, but the settings are only useful for "sam build", afterwards they are irrelevant. Which settings are picked during "sam build"? There seems to be a plenty which could be...

Yes, I use "Directory.Build.Props" too, in order to set common properties for all projects in a common "devkit", which typically is a solution container (I often share projects across solutions)....

In fact, I observe the following unexpected(?) behavior: if `ApiKeyRequired` attribute exists and is set to the result of the expression then it is always 'true' no matter what the...

> We can also use [if-expressions](https://jinja.palletsprojects.com/en/2.11.x/templates/#if-expression) > > ```shell > $ cat conditional/cookiecutter.json; tree conditional; cookiecutter -f --no-input conditional; tree sceletor > { > "project_name": "sceletor", > "generate_this": "y" >...

Yes. This makes the extension unusable for multi-root workspaces with non-trivial number of projects.