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
The workspace implementation of calendarize is (partly) broken. The index generation itself works fine, but actions like publish and discard are not properly handled anymore. Some indices are not properly cleaned up anymore etc., specifics need to be investigated.
Scenarios to be tested:
Create new event in workspace 'version' => ['action' => 'new']
Discard workspace version 'version' => ['action' => 'clearWSID']
a: Event + Configuration
b: only Configuration
Delete event in workspace
I highly suggest creation functional tests triggering the DataHandler with cmd- and datamaps (see here). It makes sense to "capture" these from real request as use them for test cases.
Another point to improve:
Overwriting the class WorkspaceRemoteServer is quite an intrusive way. It only hides the indices from being displayed in the BE module. Maybe this could be replaced by AfterCompiledCacheableDataForWorkspaceEvent?
The text was updated successfully, but these errors were encountered:
The workspace implementation of calendarize is (partly) broken. The index generation itself works fine, but actions like publish and discard are not properly handled anymore. Some indices are not properly cleaned up anymore etc., specifics need to be investigated.
Scenarios to be tested:
'version' => ['action' => 'new']
'version' =>['action' => 'publish', 'swapWith' => xyz,]
'version' => ['action' => 'clearWSID']
I highly suggest creation functional tests triggering the
DataHandler
with cmd- and datamaps (see here). It makes sense to "capture" these from real request as use them for test cases.Where to start:
processCmdmap_discardAction
to handle deletion properlyswap
does not exist anymoreAnother point to improve:
Overwriting the class
WorkspaceRemoteServer
is quite an intrusive way. It only hides the indices from being displayed in the BE module. Maybe this could be replaced byAfterCompiledCacheableDataForWorkspaceEvent
?The text was updated successfully, but these errors were encountered: