89527eaf86
It was impossible to explicitly provide attribute owner class to
getAttr/setAttr methods without using namespace prefix or if the
type was not from the core library.
The problem is a combination of 2 issues:
* There was no yaql smart-type specification for the parameter.
So the type passed as string remained to be string rather than
MuranoClassReference.
* MuranoTypeName smart-type used current type package to
lookup MuranoClass instance by its name. Because getAttr/
setAttr are located in core library it couldn't find types that
are not in core library. To solve this now all python methods
have special metadata key so that we could distinguish
methods that run in new context from global yaql functions
that use the same smart type but run in caller context. In former
case (which is the case for getAttr/setAttr) it now uses caller
type rather than the current (io.murano.Object in this case).
Change-Id: Ie87deb06bde498a7930bc617da323491855466c5
Closes-Bug: #1532800
10 lines
363 B
YAML
10 lines
363 B
YAML
---
|
|
features:
|
|
- Now all native MuranoPL methods (those that are written in Python)
|
|
have "?muranoMethod" metadata key referring to MuranoMethod instance for
|
|
the method.
|
|
fixes:
|
|
- It was impossible to explicitly provide attribute owner class to
|
|
getAttr/setAttr methods without using namespace prefix or if the type was
|
|
not from the core library.
|