Open Lowcode
Open Lowcode
The LargeBinaryArgument (org.openlowcode.design.data.argument) should be hardcoded as not a security argument. It does not make sense to have a LargeBinaryArgument as security argument
There is a setting in property org.openlowcode.design.data.properties.basic.DisplayLinkAsAttributeFromLeftObject allowing to choose if query is done by number or name. This feature should be implemented
The ExternalElement class (org.openlowcode.design.data) contains attributes that are not used. The class could probably be simplified
The UniversalStartNode class in smart report is not complete. It should be completed to be operational org.openlowcode.design.advanced.UniversalStartNode
The MainReportValue is using an empty ValueConsolidator class that does not seem to be used. It could probably be removed entirely. (org.openlowcode.design.advanced.MainReportValue)
The LeftForLink property (org.openlowcode.design.data.properties.basic) has a method addActionOnObjectId that probably does not make sense as it refers the left object of the link. There is no reason to add such...
The designer (org.openlowcode.design) uses generics for objects, properties... Those generics are inconsistent, and should be reviewed to be either suppressed or kept and used systematically.
In Open Lowcode designer, The MethodArgument method does not seem to add any value compared to the ArgumentContent class. Method Argument should be replaced everywhere by ArgumentContent. This will not...
A DataObjectElement (org.openlowcode.design.data.DataObjectElement) has several methods that are actually useful for fields (that have a single element shown in object) but not properties. This includes displayname and tooltip. Tholse fields...
A DataObjectElement (org.openlowcode.design.data.DataObjectElement) asks subtypes to implement a method (writeDependentClass) where import statements are directly written in the data object source code. As data object elements are likely called several...