william: Author Summary
| Build | Completed | Code Changes | Tests |
|---|---|---|---|
| GDS › GDSNB › #233 | 6 hours ago | 345 passed | |
| GDSCP › GDSCPN › #256 | 7 hours ago |
GDS-989 BypassTideMerge does not work with Spring proxies
Also was not implemented on methods for non MVC Spring context GDS-976 FormValidator does not work with deep properties
When binding the validator to a non root binding (i.e. {model.subModel}) the detected property bindings don't have the correct path. As it's not possible to automatically detect the root binding, a new property entityPath is added to FormValidator. Minor changes
GDS-982 FormValidator incorrectly disambiguates existing bindings
Added a priority system : bidirectional bindings are now considered first, then unidirectional bindings. The user can also define a list of property names that will always be considered as input property (such as text, selectedDate...). GDS-977 DataNucleusExternalizer depends on JPA
There are hard compilation dependencies on JPA classes (annotations). They are not evaluated at runtime by reflection. |
345 passed |
| GDS › GDSNB › #232 | 1 day ago |
GDS-997 Don't overwrite initialized entity with lazy proxy
When not using optimistic locking, initialized entities are always overwritten by proxies. There is probably no rationale for this and it causes other issues. Also dirty state is not cleared any more when merging a proxy as the local state has no reason to have been changed during merge as we received an uninitialized object. GDS-998 Tide: reset does not work as expected with collections when they have been modified
Important change: dirty checking now stores the collection indices unchanged in event locations instead of adjusting them with removals/additions The adjustment is done later when comparing saved events to incoming local changes Merge branch 'master' of ssh://github.com/graniteds/graniteds
GDS-997 EntityManager objectEquals uses === for identifier equality
This breaks proxy merging when id is a Long and not a Number/String |
345 passed |
| GDSCP › GDSCPN › #255 | 1 day ago |
GDS-997 Don't overwrite initialized entity with lazy proxy
When not using optimistic locking, initialized entities are always overwritten by proxies. There is probably no rationale for this and it causes other issues. Also dirty state is not cleared any more when merging a proxy as the local state has no reason to have been changed during merge as we received an uninitialized object. GDS-998 Tide: reset does not work as expected with collections when they have been modified
Important change: dirty checking now stores the collection indices unchanged in event locations instead of adjusting them with removals/additions The adjustment is done later when comparing saved events to incoming local changes Merge branch 'master' of ssh://github.com/graniteds/graniteds
GDS-997 EntityManager objectEquals uses === for identifier equality
This breaks proxy merging when id is a Long and not a Number/String |
345 passed |
| GDSCP › GDSCPN › #254 | 2 days ago |
GDS-988 Spark collections use s:SortField and not mx:SortField
PagedCollection casts all sort/fields as mx:SortField which does not work with Spark components GDS-1002 Provide SortableAsyncListView component
Default AsyncListView is broken and does not propagate sort elements from the UI to the data provider |
342 passed |
| GDS › GDSNB › #229 | 2 days ago |
GDS-988 Spark collections use s:SortField and not mx:SortField
PagedCollection casts all sort/fields as mx:SortField which does not work with Spark components GDS-1002 Provide SortableAsyncListView component
Default AsyncListView is broken and does not propagate sort elements from the UI to the data provider |
342 passed |
| Build | Completed | Code Changes | Tests |
|---|---|---|---|
| GDS › GDSNB › #233 | 6 hours ago |
GDS-989 BypassTideMerge does not work with Spring proxies
Also was not implemented on methods for non MVC Spring context GDS-976 FormValidator does not work with deep properties
When binding the validator to a non root binding (i.e. {model.subModel}) the detected property bindings don't have the correct path. As it's not possible to automatically detect the root binding, a new property entityPath is added to FormValidator. Minor changes
GDS-982 FormValidator incorrectly disambiguates existing bindings
Added a priority system : bidirectional bindings are now considered first, then unidirectional bindings. The user can also define a list of property names that will always be considered as input property (such as text, selectedDate...). GDS-977 DataNucleusExternalizer depends on JPA
There are hard compilation dependencies on JPA classes (annotations). They are not evaluated at runtime by reflection. |
345 passed |
| GDSCP › GDSCPN › #256 | 7 hours ago |
GDS-989 BypassTideMerge does not work with Spring proxies
Also was not implemented on methods for non MVC Spring context GDS-976 FormValidator does not work with deep properties
When binding the validator to a non root binding (i.e. {model.subModel}) the detected property bindings don't have the correct path. As it's not possible to automatically detect the root binding, a new property entityPath is added to FormValidator. Minor changes
GDS-982 FormValidator incorrectly disambiguates existing bindings
Added a priority system : bidirectional bindings are now considered first, then unidirectional bindings. The user can also define a list of property names that will always be considered as input property (such as text, selectedDate...). GDS-977 DataNucleusExternalizer depends on JPA
There are hard compilation dependencies on JPA classes (annotations). They are not evaluated at runtime by reflection. |
345 passed |
| Build | Completed | Code Changes | Tests |
|---|
Also was not implemented on methods for non MVC Spring context
When binding the validator to a non root binding (i.e. {model.subModel})
the detected property bindings don't have the correct path.
As it's not possible to automatically detect the root binding, a new
property entityPath is added to FormValidator.
Added a priority system : bidirectional bindings are now considered
first, then unidirectional bindings.
The user can also define a list of property names that will always
be considered as input property (such as text, selectedDate...).
There are hard compilation dependencies on JPA classes (annotations).
They are not evaluated at runtime by reflection.