On Wed, 10 Jun 2020 11:37:02 +0200 (CEST)
"Richard Weickelt" wrote:
> ... And module properties set in the profile. I had a glance look at the
> source code. When evaluating the condition property, we are taking the
> following information from the product context into account:
>
> - module
> And of course the module's own properties set in the module file, except
> those referring to probes. But we do evaluate the module condition in a
> product context. Is that not the real product context or at least very
> close? E.g. if product sets moduleX.propA to true and depends on moduleX,
Christian Kandeler wrote on 10. June 2020 10:09 (GMT +02:00):
> On Tue, 9 Jun 2020 20:55:43 +0200
> Christian Gudrian wrote:
>
>> Could it be that only a restricted set of variables is available during
>> evaluation of the module’s „condition“ property? Neither
>> „product“ nor any imported
On Tue, 9 Jun 2020 20:55:43 +0200
Christian Gudrian wrote:
> Could it be that only a restricted set of variables is available during
> evaluation of the module’s „condition“ property? Neither „product“ nor any
> imported modules’ variables can be accessed („Can’t find variable“ error).
>
> Is
