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
Creating a widget using CLI produces a designer javascript file that is not converting non string properties to string to be able to display them in the simple designer.
To reproduce:
Add 2 more public properties to the controller
public int Number {get; set;}
public bool YesNo {get; set;}
in the view display the 2 properties using input types number and checkbox using the correct syntax for Angular binding to the perspective properties.
You will notice that you can make changes to the designer but they don't show up upon return to the designer. The Advanced designer is working correctly.
Developers should not modify the js file themselves to do something as simple as converting these types to strings, it should be part of the CLI template generation automatically.
The text was updated successfully, but these errors were encountered:
Creating a widget using CLI produces a designer javascript file that is not converting non string properties to string to be able to display them in the simple designer.
To reproduce:
Add 2 more public properties to the controller
public int Number {get; set;}
public bool YesNo {get; set;}
in the view display the 2 properties using input types number and checkbox using the correct syntax for Angular binding to the perspective properties.
You will notice that you can make changes to the designer but they don't show up upon return to the designer. The Advanced designer is working correctly.
Developers should not modify the js file themselves to do something as simple as converting these types to strings, it should be part of the CLI template generation automatically.
The text was updated successfully, but these errors were encountered: