You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A Spectrum Card has a member called quickActions which is assigned a QuickActions component. It can also be assigned a Footer element. Specifying the element (sp:CardFooter) before the quickActions setter, caused the stack underflow.
Hi, I think compiler should differentiate property members from elements, and the user should be able to declare in the any order, even mixing them. Then just elements should be taken by the order of declaration.
just my 2...
I discovered a situation which results in the error above. It had me scratching my head for quite some time until I found the problem:
I had some markup which can be distilled to the following:
A Spectrum Card has a member called
quickActions
which is assigned aQuickActions
component. It can also be assigned aFooter
element. Specifying the element (sp:CardFooter
) before thequickActions
setter, caused the stack underflow.The following modification fixes the error:
I don't know if the order of the declarations is a hard requirement, but if it is, we need a better error message...
The text was updated successfully, but these errors were encountered: