@rentman/rm-core 67.0.0 → 67.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -5,7 +5,7 @@ import { TransactionCache } from '../../cache/transaction/TransactionCache';
|
|
|
5
5
|
import { ItemResource } from '../../../models/ItemResource';
|
|
6
6
|
import { BusinessLogicRuleApplyContext } from '../BusinessLogicRuleApplyContext';
|
|
7
7
|
import { RmProjectDefaultTimeResources } from '../../../services/rm-project-default-time.service';
|
|
8
|
-
declare const planningmateriaalColumns: readonly ["id", "parent", {
|
|
8
|
+
declare const planningmateriaalColumns: readonly ["id", "parent", "duur", {
|
|
9
9
|
readonly categorie: readonly ["subproject", "project"];
|
|
10
10
|
}];
|
|
11
11
|
type ConditionResult = Set<ItemId> | typeof BLR_SKIP_RULE;
|
|
@@ -26,5 +26,10 @@ export declare class SocketMessageHandler {
|
|
|
26
26
|
* If we think it fits (or maybe) we should fetch the complete item with the superset of columns (the socket message might not have all values)
|
|
27
27
|
*/
|
|
28
28
|
private processMessage;
|
|
29
|
+
/**
|
|
30
|
+
* A created item can be deleted again before its fetch returns. Its delete message is then ignored, because the
|
|
31
|
+
* item is not cached yet, so the socket values must not be applied either: the item no longer exists.
|
|
32
|
+
*/
|
|
33
|
+
private dropCreatedItemsMissingFromResponse;
|
|
29
34
|
private processRequests;
|
|
30
35
|
}
|