nullable parameter is ignored if SmartType is provided in the parameter specification

Bug #1522417 reported by Ekaterina Chernova
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ekaterina Chernova

Bug Description

While registering new function in YAQL, specification for the parameter can be provided: @specs.parameter(name, value_type=None, nullable=None, alias=None)

If value_type is specified and it is a yaqltypes.SmartType nullable is should be provided there and is ignored in the 'parameter' itself.

Need to raise in error in the parameter declaration in that case

affects: murano → yaql
Changed in yaql:
milestone: mitaka-2 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.