@rentman/rm-core 7.0.5 → 7.0.6

package/changelog.md

@@ -1,817 +1,820 @@
-#Changelog
-Contains new features, breaking changes and their reasoning
-
-## 7.0.5
-- Remove automatic fetching of derived values for not-yet-created items
-
-## 7.0.4
-- Automatically resolve derived values when a new item is created
-- Fixed a bug where `AbstractCache.getParentFromFields` would still return `null` incorrectly
-
-## 7.0.3
-- Fixed a bug where `AbstractCache.getParentFromFields` would still return `undefined` parent values
-
-## 7.0.2
-- Check if any of the parent fields (`itemtype`, `item`) is `null`, in which case it won't be treated as a valid parent in `AbstractCache.getParentFromFields`
-
-## 7.0.1
-- Ignore columns in ApiFormatter::hasChanges if the `modified` object does not contain a value for it. 
-
-## 7.0.0
-- **Breaking**: Remove `enableChangesWatcher` and `disableChangesWatcher` in `TransactionCache`.
-- Fetch lock token in `TransactionItemHandler.processItemEntryChanges`. 
-
-## 6.3.10
-- Only call `onRemove` of a collection if there are actually any items removed
-- Expand cached columns anyways if there are no items to expand in `TransactionCachedQueryHandler.__expandCachedQuery`
-
-## 6.3.9
-- Fixed a bug where deleted local items would still appear as unsaved changes
-
-## 6.3.8
-- Always fetch 'id' and 'permissions' columns so that they are always available
-
-## 6.3.7
-- Fixed a bug where items in a socket message that _might_ fit (`MAYBE`) in a collection would not be checked/added.
-
-## 6.3.6
-- Fixed a bug where `AbstractCache.fetchUpdatedDerivedValuesFromDelta` would attempt to use ItemChanges not cached on the transaction
-resulting in an error
-
-## 6.3.5
-- Fixed a bug where after creating items derived values would needlessly be refetched
-> The core now properly detect that even though an ItemId is updated (after a create) it's still the same item so no request has to be done
-- Fixed a bug where ItemEntry's would not be re-cached under their new ItemIds
-
-## 6.3.4
-- Fixed a bug where already cached itemEntries would not properly be detected when calling `ServerCache.processResponse`
-- Fixed a bug where calling `CreatedChangesDelta.remove` would add `empty` values in the array instead of removing the entry
-
-## 6.3.3
-- Fixed a bug where local ItemEntries were not properly updated after saving
-
-## 6.3.2
-- Fixed updating item entry itemId field after processing changes
-
-## 6.3.1
-
-- Fixed a bug where query with a local ID would do a request to the server
-```
-// This example should now no longer do a request
-transaction.getItemsByQuery(
-    'Tijd',
-    {
-        project: -11,
-    }
-);
-```
-
-## 6.3.0
-- Allow strict typing of `FieldMap`
-
-## 6.2.5
-- Remove overwriting itemType with itemType of rootItem during create
-
-## 6.2.4
-- Fixed a bug where items would not appear in a collection after changes propagated from a parent transaction
-
-## 6.2.3
-- Fixed a bug where `previous` would actually contain new values because the `previous` object was made after the values were already synced
-
-## 6.2.2
-- Fixed a bug in syncing of initial values after saving an item causing the item to still be marked having changes
-
-## 6.2.1
-- Fixed a bug where `ItemEntry`s created on the `ServerCache` where not matched on child `TransactionCache`s
-
-## 6.2.0
-- Fixed a bug where synchronous validators would leave the validator in `pending` state
-- Only re-match items when values are actually changed
-- Removed `defered` from `CachedQueryItem` and added `resolve` and `reject`
-- Check if ItemEntries are already created before creating new ones, if that is the case treat it like an update
-> What could happen was that a faster request created an ItemEntry for the same item as another request
-> which caused the double creation of an ItemEntry 
-
-## 6.1.3
-- Add `isPending` function to `TransactionValidator`
-- `TransactionCache`s will now be invalid until all pending transaction validators are done 
-
-## 6.1.2
-- Check if an error key exists before deleting it in `TransactionCache.clearItemError`
-
-## 6.1.1
-- Correctly pass `ErrorHandlerInterface` to `ChangesDeltaFactory`. 
-
-## 6.1.0
-- Return `ChangesDelta` instance in `setItemUpdated`, `setItemDeleted`, `setItemsDeleted` methods, and a promise that resolves to the instance in `setItemCreated` and `setItemsCreated`.
-
-## 6.0.2
-- Update `query` parameter of `getByQuery`, `getLocalByQuery`, `batchGetLocalByParent`, and `matchQuery` in `ItemCache`.
-
-## 6.0.1
-- Fixed a bug where a local item wouldn't be found when using `TransactionCache.getItemByState` on a child transaction
-
-## 6.0.0
-- Refactored query caching structure
-- Properly implemented `limit` in collections
-- Removed extending of collections
-
-## 5.0.1
-- Add 'icon' column type to non-selectable column types
-
-## 5.0.0
-- Fixed a bug where created, creator and permissions was always set to default values
-- **Breaking:** Remove `onItemsCreated` collection callback.
-
-## 4.0.4
-- Fixed a bug where ModuleChangesCompilation wouldn't include all changes
-
-## 4.0.3
-- Local collections are now correctly identified when using a local ID in a linkTo request instead of the `parent` option
-- Fix issue where local collection entries were not moved to server cache after save.
-
-## 4.0.2
-- Fixed a bug where clearing collections would error after saving a transaction
-
-## 4.0.1
-- Remove thrown error in `ItemResource.callOnChange`
-> The frontend still relied on this and we won't refactor that at this point
-
-## 4.0.0
-- Removed `ItemResourceOptions.onChange`, this is replaced by `TransactionCache.registerFieldChangeCallback`
-> Because the `onChange` is no longer stored on the ItemResource, the ItemResource doesn't have to be cached.
-> This way you don't have to call `ItemResource.clearResource` anymore (you do need to deregister the fieldChange callbacks)
-
-## 3.1.0
-- **Breaking:** Remove `fields` property, add `getFields` method in `Template` class.
-- **Breaking:** Add `ConversionMapService`. Update `updateItemValues` to take a `source` and `destination` parameter.
-- Update `entry.itemId` for items created items in `TransactionCache.getDelta`.
-> This fixes an issue with updating IDs of local items.
-- Add dependency interfaces for `AbstractCache`, `ServerCache`, `TransactionCache`, `TransactionCollectionHandler`, `TransactionItemHandler`.
-- Add `CreatedChangesDelta` class, which replaces the `created` component of the `ChangesDelta` and includes some query methods. Add `isEmpty` method to `ChangesDelta`.
-
-## 3.0.1
-- Fixed a bug where the `StateKeyType` enum couldn't be used when imported
-
-## 3.0.0
-- Remove ViewResource, EditResource, CollectionViewResource and CollectionEditResource
-> There was no real distinction between them anymore since the core 2.0 update.
-> You can now use the base ItemResource and CollectionResource types instead
-
-## 2.4.0
-- Update Typescript version to `3.7.2`, also update other plugins 
-
-## 2.3.0
-- Add callbacks when errors are set/cleared to `TransactionEventHandler`
-- Added the possibility to differentiate between errors to display below a field and on the save button in `TransactionValidator`
-- Changed the format of the error translations from `string` to `() => string` in `TransactionValidator`
-> Now the translation function will only be called when the error is actually set, not when it's cleared
-
-## 2.2.1
-- Fixed a bug where resolving derived values for new items (in `TransactionCache.applyChangesDelta`) would sometimes error
-
-## 2.2.0
-- `ChangesDelta.setItem(s)Created` will now accept incomplete input values
-> It will now fetch a template for you and process the items, so you no longer need to do that yourself
-
-## 2.1.2
-- Fixed a bug where deleted ItemEntries weren't picked up when detecting transaction changes
-
-## 2.1.1
-- Fixed a bug where an ItemEntry's errors wouldn't be deleted when the ItemEntry was deleted on a transaction
-
-## 2.1.0
-- Refactor `TransactionCache.getItemsByQuery` to check cached entries (just like a collection)
-- Add `TransactionValidator`, allow passing of a `TransactionValidatorFactory` to a transaction
-> You can use these validators to set errors using `setItemError` and `setGlobalError`
-- Fixed a bug where `TransactionItemHandler.cloneItemEntry` could only clone entry with changes on the target transaction.
-> It will not look for changes recursively on the transaction change
-
-## 2.0.19
-- Ensure all requestColumns for newly created ItemEntries from a template are available
-- Ensure derived values for newly created ItemEntries from a template are available
-
-## 2.0.18
-- Include read-only columns when detecting changes in TransactionItemHandler.processItemEntryChanges
-> Read-only columns shouldn't count as changes on the tab, but they should be taking into account when deciding whether or not to call `onChange`
-
-## 2.0.17
-- Fixed a bug where deleting an item that isn't in the transaction's item entry cache would result in an error
-- Fixed a bug where response columns weren't set for newly created local CollectionEntries
-- Fixed a bug where items weren't matched for newly created local CollectionEntries
-
-## 2.0.16
-- Fixed a bug where queries with a link to a local parent item weren't updated on save
-
-## 2.0.15
-- Cache ItemEntries that fit collections on the CollectionEntry's query instead of the CollectionEntry's id
-- Add a 'hint' to ChangesDeltas which allows skipping the extra request to validate `maybe` query matches
-- Create transaction changes for ItemEntry updates in the changesDelta if non exist yet when calling `TransactionCache.applyChangesDelta`
-> This allows you to update values on a transaction without having to fetch a resource for it by calling
-> `ChangesDelta.setItemUpdated()`
-
-## 2.0.14
-- Fixed reading of derived values in `getItemIdByColumn` when a ChangesDelta is passed  
-
-## 2.0.13
-- Fixed a bug where the incorrect fields where applied to the ChangesDelta in `TransactionItemHandler.cloneItemEntry`
-- A RequestBuffer's promise will now resolve after the ServerCache.processResponse promise is done, ensuring all values are present before continuing
-- Request columns for the request ItemType will now properly be taken into account in ServerCache.processResponse ensuring root columns are always properly set. (This is used to update derived values) 
-
-## 2.0.12
-- Fixed a bug where created changes weren't copied to the itemchanges
-- Only take readonly parent columns instead of all readonly columns in `ApiFormatter.hasChanges`
-- Fixed a bug where ItemEntry's where still in `ItemCache.entriesByEntryId` after clearing them
-
-## 2.0.11
-- Fixed a bug where changes weren't copied to the itemchanges
-- Fixed correct isCalledAfterApiSave values on calls to ServerCache.processResponse
-
-## 2.0.10
-- Construct `ColumnSet` with proper `requestColumns` when creating a `Template` with additional columns
-
-## 2.0.9
-- Properly process linked items from the template request in `TransactionItemHandler.createItems`
-
-## 2.0.8
-- Fixed a bug where not all fields where available even tough an ItemResource with specific columns was created
-
-## 2.0.7
-- Define abstract copyTransactionItemEntryChanges on ItemHandlerBase
-- Implement copyTransactionItemEntryChanges on TransactionItemHandler and ServerItemHandler
-- Fix AbstractCache/ServerCache/TransactionCache `getParent` function arguments
-> With the newly added arguments the function definitions didn't align anymore causing typescript errors
-> Even though the arguments aren't used in the `ServerCache` they're added in there
-
-## 2.0.6
-- Remove `ApiFormatter.lazyClone`
-> You can't lazily clone moment objects because the moment you wanted to clone could be changed in the time the getter isn't invoked, resulting in a different value
-
-- Create a copy of the child transaction's field instead of copying the object reference in `TransactionCache.applyChangeFromChild` and `ChangesProcessor.executeCreateRequest`
-> When writing to the object references you're changing multiple transactions at once, while this should be handled by applyCHangesFromParent
-
-## 2.0.5
-- Add `callOnAddWithInitialItems` option to `CollectionResourceOptions`
-> If `true` the `onAdd` callback will be called with the initial set of items
-
-
-## 2.0.4
-- Add `isCalledAfterSocketUpdate` to `onAdd`, `onRemove` and `onChange` callbacks
-> You can use this if a data change should only trigger an action when the user caused it himself 
-
-## 2.0.3
-- Fix `CollectionEditResource.removeItems`
-- Move `getCurrentCollectionEntryCache` and `getCurrentItemEntryCache` from `TransactionCache` to `AbstractCache`
-
-## 2.0.2
-- Fix marking entries as deleted and compiling this into a request
-
-## 2.0.1
-- Expand CollectionEntry's columns in `ServerCollectionHandler.fetchCollectionData`
-
-## 2.0.0 - Major caching refactor
-- Completely reworked internal caching structure, see [this Confluence page](https://rentman.atlassian.net/wiki/spaces/DEV/pages/704872456/) for the motivations behind it.
-
-
-## 1.9.0
-- Don't create ItemResources when not returning links in `ItemAdministrator.getNewResourceWithId` and in `ItemAdministrator.constructOnItemsExpanded` 
-
-## 1.8.0
-- Remove `ResourceCache` and `resourceLevel`
-> You should now manually call `resource.clearResource` when you no longer need a resource
-- Add `onConstruct` function to `ItemResource` and `CollectionResource`
-> This is overwritten by the frontend to track resource creation
-
-## 1.7.6
-- Add priority parameter to local cache callbacks. The callback condition (`always` / `onClose` / `skipOnClose`) no longer has any effect on the order in which the callbacks get executed.
-- **Breaking:** Remove `LocalCacheCallbackCondition` enum.
-- Add `itemId` parameter to `ItemHandler.fetchNewItem`. An error is thrown when an ID already exists.  Add `getNewResourceWithId` to ItemAdministrator. Deprecate `getItemByState`.
-
-## 1.7.5
-- For template column sets it is no longer assumed all columns are present. This fixes an issue with incomplete column
-sets in the front-end.
-- Fix issue where `changesProcessor` instance was undefined in `itemResourceFactory` and `collectionResourceFactory`.
-Create variables for each core service in order to get a TypeScript error when a dependency hasn't been initialized yet.
-
-## 1.7.4
-- Add support for strict ItemType type checking in `FieldMap` 
-
-## 1.7.3
-- Add support for strict ItemType type checking
-> This is temporarily defaulted to `any` to prevent compile errors in the frontend 
-
-## 1.7.2
-- Fix some typing issues in:
-    - ApiResponseProcessor
-    - ItemCache
-    - KeyService 
-
-## 1.7.1
-- Fix issue where `CreateRequestFactory` would be undefined in `ChangesProcessor`.
-
-## 1.7.0
-- **Breaking:** remove `ChangesProcessorFactory`. Add `ChangesProcessor` instance to core directly. 
-
-### Resource caching
-- **Breaking:** the following properties are removed:
-    - On `ItemEntry`: `clearResources`, `deactivateResources`.
-    - On `CollectionEntry`: `clearResources`, `getCurrentResource`.
-    - On `CollectionResourceOptions`: `clearOnTabChange`, `clearOnSubTabChange`.
-- An additional `level` parameter has been added to all methods that return resources. 
-- When creating resources using `ItemResourceFactory` or `CollectionResourceFactory`, this parameter is mandatory.
-A `defaultResourceLevel` parameter has been added to the `LocalCache` constructor.
-- A `clearResources` method has been added to `ItemAdministrator`. When calling this method, all item / collection
-and collection resources with a level of `level` or higher will be removed.  
-- The `clearResources` method has been removed from `LocalCache`.
-- The `setCurrentLocalCache` function has been removed from `LocalCacheManagerInterface`.
-
-## 1.6.13
-- When encountering a collection entry with `PROMISED_EXPAND` status, call `getCachedEntryStatus` after the initial
-promise has been resolved.
-
-> This is the likely cause of the issue where `_resolve` is called on a non-deferred collection entry.
-
-## 1.6.12
-- Fix error that occurs when trying to resolve a non-deferred collection entry.
-
-## 1.6.11
-- Fix issue where `QueryMatcher.matchComplexQuery` would return the wrong value.
-
-## 1.6.10
-- **Breaking**: Remove `linkType`, `linkIdArray` properties from `LinkCollectionDefinition`. Add `linkType`,
-`linkIdArray` parameters to `ItemAdministrator.getLinkCollectionsFromDef`.
-
-## 1.6.9
-- Redeploy of `1.6.8`
-
-## 1.6.8
-- Add support for `not` in queries
-
-## 1.6.7
-- Fix issue where `CollectionMatcher.addToCollections` wouldn't return the correct type.
-
-## 1.6.6
-- Add `callOnAdd` parameter in `CollectionHandler.batchExtend`. Set `updateInitial` to true. Remove `updateInitial` parameter in `CollectionEntry.extend`, as it should always be true.
-> The `extend` function only concerns itself with remote items, so no local changes should be generated.
-
-## 1.6.5
-- Fix issue where a derived column could be marked as the `link` (parent) column in the column set.
-> This could lead to instances where a different column would be set to the value of the parent.
-
-## 1.6.4
-- Fix issue where the `onChange` collection callback would not be called when updating it in the options.
-- Add `callOnAdd` parameter to collection matcher. When set to `false`, `onAdd` is not called for the `resultCollectionResource`.
-
-## 1.6.3
-- Properly type ApiResponseProcessor - fetchObjectArray
-
-## 1.6.2
-- Fix issue where the collection handler would return collection entries before they were resolved when calling `batchFetch`.
-
-## 1.6.1-3
-- Check for linkedTo before checking for subqueries in QueryMatcher
-> Linkedto also has `.query` and was incorrectly marked as a subquery 
-
-## 1.6.1-2
-- Fixed shorthand query with null values
-> The QueryParser would incorrectly identify subqueries when using null in a shorthand
-
-## 1.6.1-1
-- Fixed shorthand query with Moment values
-> The QueryParser would incorrectly identify Moment objects as a subquery
-
-## 1.6.1
-- Added support for subqueries in QueryParser and QueryMatcher
-> Collections using subqueries will always return 'maybe' in the QueryMatcher
-
-## 1.6.0
-- All external callbacks are now wrapped in a `try ... catch` block. This prevents them from breaking core functionality. 
-- **Breaking**: Add `ExceptionHandlerInterface` parameter to core constructor. 
-
-## 1.5.9
-- Fix issue that occurs when trying to resolve a `ColumnSet` using a single non-existing column.
-Catch exceptions that might occur when resolving an `ItemEntry`.
-- Add `mergeRequestColumns`, `mergeResponseColumns` to `ColumnSet`. When encountering new items while expanding a collection, add them to the collection.
-
-## 1.5.8
-- Introduce `RemoteViewResource` and `LocalViewResource`.
-> The `fields` property of a `RemoteViewResource` represents
-server values, while the `fields` property of a `LocalViewResource` represents local values.
-- The `fields` property of a `ViewResource` is now read only.
-
-## 1.5.7-1
-- Make ItemResource/CollectionResource base class abstract
-- Add missing overload functions in some places
-- Fix default comparator `QueryMatcher.parseSimpleQuery`
-- Fix `ExtendedCollectionMatchResult` `collection` property type 
-
-## 1.5.7
-- Properly type Collections & ItemResources (and return values) in the whole core.
-> The core will now properly return Collections & ItemResources based on the passed CollectionOptions.
-> You can now also type the expected collection type
-
-``` 
-// Expects a collection with editCollection and editItems both `true`
-// Will properly return EditResources for all collection functions
-const collection: CollectionEditResource<EditResource>;
-
-// other variations are:
-// CollectionViewResource<ViewResource>
-// CollectionViewResource<EditResource>
-// CollectionEditResource<ViewResource>
-
-this.core.itemAdministrator.getCollection(
-	'Notitie',
-	{
-		editCollection: true, // Will return a CollectionEditResource 
-		editItems: true // Will return EditResources instead of ViewResources in `.items`
-	}
-)
-```
-
-## 1.5.6
-- Add `getAllLocalCaches` to `LocalCacheManagerInterface`, remove item entries from all local caches on socket delete.
-
-## 1.5.5
-- Add 'order' column type handling to ApiFormatter functions
-
-## 1.5.4
-- Fix issue where parent would be incorrectly set when cloning a single item.
-- Type functions related to expansion maps in `ItemEntryService`. 
-
-## 1.5.3
-- Fix issue where the `enableSave` collection resource option would default to `false`. This would throw an error when
-calling `save` on a collection resource where this option was not explicitly set. 
-
-## 1.5.2
-- Type functions in `ColumnUtil` class.
-- Add `getRequestColumnId` and `containsDerivedColumns` to `ColumnUtil`.
-> `getRequestColumnId` should be used instead of `Util.getFirstProperty` when retrieving a column ID.
-- **Breaking:** Remove `ColumnUtil.isColumnSubset`. Use `ColumnSet.isSuperSetOf` instead.
-- Remove `findColumnObject`. Rename `findColumn` to `findRequestColumn`. 
-
-## 1.5.1
-- Properly remove item entry stub from (local) cache when request fails.
-- Fix issue where item or collection options could be set to undefined.
-
-## 1.5.0
-- Add `SocketMessage` type and add types to `SocketMessageHandler`
-- Expand local items requested using `getItemById` or `getItemsById` in `ItemAdministrator`.
-(`fetchItem` or `fetchItems` in `ItemHandler`.)
-- Implement expanding of local collections. This no longer leads to invalid requests.
-- **Breaking:** The `expand` function in `CollectionEntry` now has an `ItemCache` parameter.
-- **Warning:** This version contains major changes.
-
-### Introduce typing of item and collection options
-- **Breaking:** Removed `QueryItemType` collection entry option.
-- **Breaking:** Removed `ItemResourceService`. 
-- Removed `processOptions` parameter from `createCollectionResource` (`ItemAdministrator`). It is now equivalent to
-`addCollection`.
-- When creating an item resource using `ItemResourceFactory`, a collection entry using `CollectionResourceFactory` or a
-collection resource using `CollectionResourceFactory` it is no longer necessary to process options beforehand. It is
-still necessary when interacting with `CollectionHandler` or `ItemHandler` directly.
-
-## v1.4.0
-- Add `expandProcessLinkedItems` and `expandAddToCollections` to `ItemAdministrator`. These are analogues to
-`processLinkedItems` and `addToCollections`, but also expand the items with (derived) values and columns as necessary.
-They have a slightly different type signature.
-- Whenever a collection is requested, the `CollectionHandler` now makes sure that added local items are expanded as
-necessary.  
-- **Breaking:** Last parameter of `ItemHandler.createLocalEntries` is now a callback function.
-- **Breaking:** Rename `TemplateLinkedItemEntryMap` type to `TemplateItemEntryMap`.
-
-## v1.3.8
-- Add `isSaving` to `LocalCache`
-> We use this to disable the cancel/save buttons while the localCache is saving in the frontend
-
-## v1.3.7
-- Fix issues that generate invalid requests / changes when moving existing item to another collection, then deleting the parent.
-- Remove slip workarounds
-- Add api request types
-- Add types to `ModuleChangesCompilation`
-
-## v1.3.6
-- Skip add / remove collection callbacks when calling `revertChanges` (`LocalCache`).
-
-## v1.3.5
-- Fix issue where items added to collections when resolving wouldn't be removed in `revertChanges` (`LocalCache`).
-
-## v1.3.4
-- Add country to isFilteredColumn in ColumnUtil
-
-## v1.3.3
-- Move processLocalConfigColumns and consolidateColumns from ColumnUtil to frontend
-> These functions are specifically used for rendering ui-grid in the frontend, so there's 
-no reason to have them in the core
-
-## v1.3.2
-- Fix types path in package.json
-
-## v1.3.1
-- Fix types path in package.json
-
-## v1.3.0
-- Rename PromiseInterface to PromiseLibraryInterface
-> PromiseInterface is now used for the internal promise type
-
-- Use PromiseInterface instead of Promise as internal promise type
-> This allows us to overwrite the PromiseInterface definition in the frontend indicate usage of ng.IPromise
-
-## v1.2.9
-- Call processOptions in fetchDerivedValuesByColumn
-> Bug was introduced earlier but got enabled in v1.2.7
-
-## v1.2.8
-- Add toJSON methods for ItemResources, ItemEntries, and ColumnSets to fix circular dependencies in JSON.stringify
-
-## v1.2.7
-- Set itemEntry parent when generating a stub
-
-## v1.2.6
-- Fix an issue introduced in v1.2.5.
-
-## v1.2.5
-- When a local item cannot by found, return a newly created item in `getItemByState` (`ItemAdministrator`) only. This
-solves an issue with refreshing on a local edit view.
-
-## v1.2.4
-- **Breaking:** When a local item cannot by found, instead of a new item being created an error is thrown. This means it
-is no longer possible to create local items using `getItemById` or `getItemsById` in the `ItemAdministrator` class.
-- **Breaking:** Removed `getItemDefinition` and `getItemByDef` in the `ItemAdministrator` class. Added `getItemByState`.
-- Renamed types `TemplateResponseItemEntryMap` to `TemplateItemEntryMap` and `TemplateResponseLinkedItemEntryMap` to
-`TemplateLinkedItemEntryMap`.
-- Removed `getCollectionCacheKey` in `KeyService`. (Legacy code.)
-
-## v1.2.3
-- Fixed issue where derived values deeper than one layer couldn't be resolved.
-
-## v1.2.2
-- Fixed issue where in derived values weren't set after create request.
-
-## v1.2.1
-- **Breaking:** Replaced the `initial` parameter with the `callOnChange` parameter (`true` by default) in the `commit`
-function of the `EditResource` class.
-- Fixed issue in `setLocalFields` (`ItemEntry`) where some values were wrongly assumed to be present in `initialValues`.
-- Optimization: Disabled automatic resolution of derived values in `addItems` (`CollectionEditResource`) when `modInstant` is set to true.
-
-## v1.2.0
-- **Breaking:** When calling `addItems` or `addItem` on the `CollectionEditResource` class derived values are now
-resolved automatically. Instead of a compound object like `{fields: {key: 'value'}, derived: {}}` an object like
-`{key: 'value'}` should now be used as argument when calling these functions.
-- **Breaking:** Added `localCache` parameter to `CollectionResource` constructor.
-
-## v1.1.20
-- Fixed minor issue where collection wouldn't be deferred properly before expanding.
-- `onChange` is now called automatically when when calling `commit` on an edit resource. 
-
-## v1.1.19
-- **Breaking:** Renamed `getCurrentChanges` to `getModuleChanges` in the `ItemAdministrator` class. Added optional
-`localCache` parameter.
-
-### Local cache callback refactoring
-- Removed `onSaveWithoutClosing` event.
-- Added `condition` parameter to `onBeforeSave` and `onSaveSuccess` (possible values are `always`, `onClose` or
-`skipOnClose`, defaults to `always`). Callbacks registered with `condition: always` will get executed before other
-callbacks.
-- Pass the local cache itself to all registered callback functions. Pass the item ID conversion map as second argument
-to `onSaveSuccess` callback functions.
-
-## v1.1.18
-- Calling `expand` on a `CollectionEntry` manually no longer defers the collection entry.
-- The `batchFetch` and `batchExpand` functions in the `CollectionHandler` class now properly defer and resolve the
-collection entries.
-
-## v1.1.17
-- Fixed issue where the `getLocalByQuery` function in the `ItemCache` class wouldn't return any items.
-- When batch resolving collection entries, `CollectionHandler` now looks for matching items using `getByQuery` instead
-of `getByParent`.
-
-### Cache invalidation
-- Added `queueReload` function to `ItemEntry` class. This will reload the item when the item entry itself or a
-collection entry containing the item is requested.
-- The `queueReload` function in the `CollectionEntry` class no longer directly defers the item.
-- Added `invalidateCache` function to the `ItemAdministrator` class. This will call `queueReload` on all item entries
-and collection entries.
-
-### Item entry refactoring
-- Renamed `process` to `setFields`. 
-- Replaced `processLocal` with `setLocalFields`. This function no longer has a `modified` parameter.
-- `setModified` now also sets local default values.
-- Removed `setCreator`. This function was called twice in some instances.
-- **Breaking:** Added `derived` parameter to `updateFields`  
-
-##v1.16
-- Pass `hasChanges` as second argument to `onBeforeSave` callbacks in  the `LocalCache` class. This fixes an issue with
-project financial values in the front-end. [RM4-9577]
-- Added `callOnActivate` parameter to `addItems` function in `CollectionEditResource` class. Use this to prevent items
-from being added to the local cache.  
-
-##v1.15
-- Fix `fetchItemTypesTranslations` function in `ColumnHandler` class.
-- Fix type definition of `PromiseInterface.all`.
-
-##v1.14
-- The `ChangesCompiler` now always processes local collections. (Even if they don't have edit resources.) This fixes an
-issue with recurring appointments in the front-end.
-
-##v1.13
-- Add option to exclude itemTypes during createLocalEntries.
-
-##v1.12
-- **Breaking:** `ItemResource.isNew` returns true *only* if the resource was created using 
-`ItemAdministrator.getNewResource` or `ItemAdministrator.getItemByDef`. This fixes an issue where items where removed
-from the local cache inadvertently.
-- The `start`, `commit` and `rollback` functions of `EditResource` now return the resource itself to facilitate chaining.
-- When calling `CollectionEntry.revertChanges`, callbacks like `onAdd` / `onRemove` and `onActivate` / `onDeactivate`
-are now respected. This fixes an issue where items where *not* removed from the local cache.
-- When removing *local* items from collections, they are removed from `initial` as well as `modified`. This fixes an
-issue where changes were being detected continuously.
-- Updated the order of requests in `changesProcessor`. The `update` request is now executed before the `delete` request,
-except when updating documents. This fixes several issues.
-- `CollectionCache` now uses a map instead of an array to store collections. This fixes an issue where the same
-collection was added multiple times.
-- Updated all models to use dependency objects. This increases ease of debugging.
-
-##v.1.11
-- Fixed issue that occurs when saving when having an existing item refer to a newly created item.
-- **Breaking:** Removed `ItemResourceService.isNewResource`.
-- **Breaking:** Renamed `ItemResource.isNewResource` to `ItemResource.isNew`. Removed parameter.
-- `ItemResource.isNew` is equivalent to `ItemResource.isLocal`, while `EditResource.isNew` checks also checks for
- completed transactions. 
-
-##v.1.10
-- Fixed issue where changes on different subtabs were not detected.
-
-##v1.1.9
-- Exposed `noop` function on `RmCore` class.
-> This is used in order to check whether a callback has a default value. 
-- Added `copyRequestColumns` function to `ColumnUtil` class.
-- Made parameters of `ItemAdministrator.saveCurrentLocalCache` and `LocalCache.save` optional.
-- **Breaking:** Reordered parameters of `ChangesProcessor.execute` to be consistent with
-`ItemAdministrator.saveCurrentLocalCache`. The new order is `singleItems` - `collections` - `parameters` -
-`breakUpByParent` - `onAfterCreateCallback`.
-
-##v1.1.8
-- Set default value for `params` to `{filter: false}` in `request` function in `ColumnHandler` class.
-
-##v1.1.7
-- Fixed issue where cached item entries or collection entries wouldn't be added to the local cache.
-
-##v1.1.6
-- Fixed issue with deferred item entries.
-- Re-enable changes watcher after save.
-- Added optional `id` parameter to `LocalCache` constructor.
-
-##v1.1.5
-- Added `clearItem` function to `LocalCache` class.
-
-##v.1.1.4
-- Fix issue where items where not added to the local cache automatically when they where added to a collection.
-> This depends on the `callOnActivate` parameter. I've added this mainly because extending collections should *not* add
-the items to the local cache.
-> In other instances this might be debatable because it doesn't do any real harm. *Not*
-doing it however can definitely be harmful. 
-
-##v.1.1.3
-- Fixed an issue where all collections in a local cache would be cleared.
-- **Breaking:** Renamed `getCacheManager` to `getCurrentLocalCache` and `setCacheManager` to `setCurrentLocalCache` in
-`LocalCacheManagerInterface`.
-
-##v1.1.2
-- Fixed an issue concerning derived values.
-
-## v1.1.1
-- Fixed an issue where changes wouldn't be detected.
-- **Breaking:** Removed the `_hasChanges` function in the `localCache` class. If you want to force changes detection,
-call `detectChanges` instead. Otherwise, rely on the `hasChanges` variable.
-- **Breaking:** Removed the `enableWatcher` and `disableWatcher` functions. Use `enableChangesWatcher` and
-`disableChangesWatcher` instead.  
-
-## v1.1.0
-### Development
-
-#### Strict TypeScript compilation
-Added the following TypeScript compiler options:
-- noImplicitThis
-- noImplicitReturns
-- strictNullChecks
-- noUnusedLocals
-- noUnusedParameters
-
-I would advise enabling these for all TypeScript projects from now on.
-
-#### Ordered imports and dependencies
-Imports are now ordered alphabetically and grouped by folder. Added a TSLint option to enforce this.
-Please note that this also applies for imports from the folder the file is currently in.
-For example, in `models/ItemResource.ts`, `itemEntry` should be imported like so:
-`import { ItemEntry } from '../models';`
-
-Also, factory and class dependencies should be ordered alphabetically as well. This will make it easier to add and
-remove dependencies in the future.
-
-### Breaking changes
-
-- Renamed `changesCompiler` to `changesCompilation`, `changesCompilerFactory` to `changesCompilationFactory`,
-`moduleChangesCompiler` to `moduleChangesCompilation` and `moduleChangesCompilerFactory` to
-`moduleChangesCompilationFactory`.
-- Removed the `allLinks` parameter from the `query` function definition in the `ApiRequestServiceInterface`. This is
-no longer supported in the back-end.
-
-#### Item and collection entries
-- Moved *all* functions that handle item entries from the `ItemEntryService` to the `ItemEntry` class.
-- Added the following functions to `ItemEntryService`:
-	- `createLocalConversionMap`;
-	- `expandLocalConversionMap`;
-	- `expandConversionMap`;
-	- `batchExpandConversionMap`;
-	- `batchClone`.
-- Cloning of item entries now works slightly differently. The function will attempt to generate a new
-item ID, and update the conversion map accordingly, but will respect the item ID that is already there.
-
-#### Rework item caching
-Newly created item entries and collection entries are no longer added to the global *or* local cache by default. 
-All entries are added to the global cache on save. Item entries are added to the local cache when resources are created 
-using the item administrator or when resources are created when adding the items to a collection.
-
-> This will increase reliability by ensuring the global cache is no longer 'polluted' with local items. Also, this will
-> allow for the creation item and collection entries without caching them directly. This is required for the copying and
-> pasting of items.
- 
-Other changes: 
- 
-- Moved `saveLocal` to `ItemAdministrator`;
-- `ItemAdministrator.fetchTitle` should now be called instead of `ItemHandler.fetchTitle`;
-- The `ItemAdministrator` collection matching functions (`addToCollections`, `removeFromCollections`) should now be
-called instead of those in the `CollectionHandler`. The `CollectionHandler` should only be used to reflect changes
-already on the backend. (Use `getCollectionMatcher`.)
-
-
-##v1.0.33
-- Really fix types path
-
-##v1.0.33
-- Fix types path
-
-##v1.0.32
-- Update `tsconfig.json` to put definitions in the root folder
-> The app had an issue with AOT compilation because of this
-
-##v1.0.31
-- Fix `columnHandler.fetchItemTypeTranslations`
-> It incorrectly looped over the response map, it should now work again
-
-##v1.0.30
-- Remove `updateTabParams` from LocalCacheManagerInterface
-> The function wasn't used
-
-- Reworked class export
-> Imports are now done from @rentman/rm-core, old imports are broken. This is because the old export structure didn't always work
-
-##v1.0.29
-- Fix inverted inArray check in CollectionEntry.removeItems
-> A delete message from the socket deleted all BUT the deleted items, this should now be fixed
-
-##v1.0.28
-Bug fixes only
-
-##v1.0.27
-- `ItemEntry.initial` is now undefined by default
-> In the SocketMessageHandler we use this check to see if an ItemEntry is a stub 
-
-##v1.0.26
-Bundle both minified and unminified code, include sourcemaps from dev build
-
-##v1.0.24, v1.0.25
-! Use version `v1.0.26` !
-
-- The core now expects a `promiseInterface` that should implement the provided `promiseInterface`
-> We need to be able to hook into the promises in order to call a digest cycle to update the ui in the frontend
-
-- Rename `ItemEntry.entryId` to `ItemEntry.id
-> It used to be called `id`, but it was changed in the seperation of the core.
-> You can use the `id` to uniquely identify an entry, since itemId can be updated (local to saved id)
-
-- Rename ItemResource `startTransaction` to `start`
-> Other functions are called `commit` and `rollback` so having 'transaction' only for start doesn't make much sense
-
-- `SocketMessageHandler.onMessageReceived` now returns a promise
-> You can now use the updated items or hook into the result to update the ui for example
-
-
-##v1.0.23
-- Rename ResourceCache to LocalCache
-> LocalCache only caches local items (name better reflects functionality)
-
-- Remove getter/setter for hasChanges
-> hasChanges is called in a digest loop in the frontend, so for performance reasons we don't want to recompute the value every time
- 
-- Remove `_getCollection` from ItemAdministrator
-> `_getCollection` is now named `getCollection` and the old `getCollection` is removed. The query is part of the
-> options and should not be given as a separate argument. This was included to support the frontend
-
-- Remove `saveCurrentTab` from ItemAdministrator
-> `saveCurrentTab` makes no sense because the core has no concept of tabs, you should use `saveCurrentLocalCache` instead
-
-- Remove `getTabEntry` and `resetTabEntry` from ItemAdministrator
-> `getTabEntry` and `resetTabEntry` make no sense because the core has no concept of tabs, you should use `getLocalCache` and `resetLocalCache` instead
-
+#Changelog
+Contains new features, breaking changes and their reasoning
+
+## 7.0.6
+Move fetching of lock from `TransactionItemHandler.processItemEntryChanges` to `TransactionCache.appyChangesDelta` to also capture creates and deletes.
+
+## 7.0.5
+- Remove automatic fetching of derived values for not-yet-created items
+
+## 7.0.4
+- Automatically resolve derived values when a new item is created
+- Fixed a bug where `AbstractCache.getParentFromFields` would still return `null` incorrectly
+
+## 7.0.3
+- Fixed a bug where `AbstractCache.getParentFromFields` would still return `undefined` parent values
+
+## 7.0.2
+- Check if any of the parent fields (`itemtype`, `item`) is `null`, in which case it won't be treated as a valid parent in `AbstractCache.getParentFromFields`
+
+## 7.0.1
+- Ignore columns in ApiFormatter::hasChanges if the `modified` object does not contain a value for it. 
+
+## 7.0.0
+- **Breaking**: Remove `enableChangesWatcher` and `disableChangesWatcher` in `TransactionCache`.
+- Fetch lock token in `TransactionItemHandler.processItemEntryChanges`. 
+
+## 6.3.10
+- Only call `onRemove` of a collection if there are actually any items removed
+- Expand cached columns anyways if there are no items to expand in `TransactionCachedQueryHandler.__expandCachedQuery`
+
+## 6.3.9
+- Fixed a bug where deleted local items would still appear as unsaved changes
+
+## 6.3.8
+- Always fetch 'id' and 'permissions' columns so that they are always available
+
+## 6.3.7
+- Fixed a bug where items in a socket message that _might_ fit (`MAYBE`) in a collection would not be checked/added.
+
+## 6.3.6
+- Fixed a bug where `AbstractCache.fetchUpdatedDerivedValuesFromDelta` would attempt to use ItemChanges not cached on the transaction
+resulting in an error
+
+## 6.3.5
+- Fixed a bug where after creating items derived values would needlessly be refetched
+> The core now properly detect that even though an ItemId is updated (after a create) it's still the same item so no request has to be done
+- Fixed a bug where ItemEntry's would not be re-cached under their new ItemIds
+
+## 6.3.4
+- Fixed a bug where already cached itemEntries would not properly be detected when calling `ServerCache.processResponse`
+- Fixed a bug where calling `CreatedChangesDelta.remove` would add `empty` values in the array instead of removing the entry
+
+## 6.3.3
+- Fixed a bug where local ItemEntries were not properly updated after saving
+
+## 6.3.2
+- Fixed updating item entry itemId field after processing changes
+
+## 6.3.1
+
+- Fixed a bug where query with a local ID would do a request to the server
+```
+// This example should now no longer do a request
+transaction.getItemsByQuery(
+    'Tijd',
+    {
+        project: -11,
+    }
+);
+```
+
+## 6.3.0
+- Allow strict typing of `FieldMap`
+
+## 6.2.5
+- Remove overwriting itemType with itemType of rootItem during create
+
+## 6.2.4
+- Fixed a bug where items would not appear in a collection after changes propagated from a parent transaction
+
+## 6.2.3
+- Fixed a bug where `previous` would actually contain new values because the `previous` object was made after the values were already synced
+
+## 6.2.2
+- Fixed a bug in syncing of initial values after saving an item causing the item to still be marked having changes
+
+## 6.2.1
+- Fixed a bug where `ItemEntry`s created on the `ServerCache` where not matched on child `TransactionCache`s
+
+## 6.2.0
+- Fixed a bug where synchronous validators would leave the validator in `pending` state
+- Only re-match items when values are actually changed
+- Removed `defered` from `CachedQueryItem` and added `resolve` and `reject`
+- Check if ItemEntries are already created before creating new ones, if that is the case treat it like an update
+> What could happen was that a faster request created an ItemEntry for the same item as another request
+> which caused the double creation of an ItemEntry 
+
+## 6.1.3
+- Add `isPending` function to `TransactionValidator`
+- `TransactionCache`s will now be invalid until all pending transaction validators are done 
+
+## 6.1.2
+- Check if an error key exists before deleting it in `TransactionCache.clearItemError`
+
+## 6.1.1
+- Correctly pass `ErrorHandlerInterface` to `ChangesDeltaFactory`. 
+
+## 6.1.0
+- Return `ChangesDelta` instance in `setItemUpdated`, `setItemDeleted`, `setItemsDeleted` methods, and a promise that resolves to the instance in `setItemCreated` and `setItemsCreated`.
+
+## 6.0.2
+- Update `query` parameter of `getByQuery`, `getLocalByQuery`, `batchGetLocalByParent`, and `matchQuery` in `ItemCache`.
+
+## 6.0.1
+- Fixed a bug where a local item wouldn't be found when using `TransactionCache.getItemByState` on a child transaction
+
+## 6.0.0
+- Refactored query caching structure
+- Properly implemented `limit` in collections
+- Removed extending of collections
+
+## 5.0.1
+- Add 'icon' column type to non-selectable column types
+
+## 5.0.0
+- Fixed a bug where created, creator and permissions was always set to default values
+- **Breaking:** Remove `onItemsCreated` collection callback.
+
+## 4.0.4
+- Fixed a bug where ModuleChangesCompilation wouldn't include all changes
+
+## 4.0.3
+- Local collections are now correctly identified when using a local ID in a linkTo request instead of the `parent` option
+- Fix issue where local collection entries were not moved to server cache after save.
+
+## 4.0.2
+- Fixed a bug where clearing collections would error after saving a transaction
+
+## 4.0.1
+- Remove thrown error in `ItemResource.callOnChange`
+> The frontend still relied on this and we won't refactor that at this point
+
+## 4.0.0
+- Removed `ItemResourceOptions.onChange`, this is replaced by `TransactionCache.registerFieldChangeCallback`
+> Because the `onChange` is no longer stored on the ItemResource, the ItemResource doesn't have to be cached.
+> This way you don't have to call `ItemResource.clearResource` anymore (you do need to deregister the fieldChange callbacks)
+
+## 3.1.0
+- **Breaking:** Remove `fields` property, add `getFields` method in `Template` class.
+- **Breaking:** Add `ConversionMapService`. Update `updateItemValues` to take a `source` and `destination` parameter.
+- Update `entry.itemId` for items created items in `TransactionCache.getDelta`.
+> This fixes an issue with updating IDs of local items.
+- Add dependency interfaces for `AbstractCache`, `ServerCache`, `TransactionCache`, `TransactionCollectionHandler`, `TransactionItemHandler`.
+- Add `CreatedChangesDelta` class, which replaces the `created` component of the `ChangesDelta` and includes some query methods. Add `isEmpty` method to `ChangesDelta`.
+
+## 3.0.1
+- Fixed a bug where the `StateKeyType` enum couldn't be used when imported
+
+## 3.0.0
+- Remove ViewResource, EditResource, CollectionViewResource and CollectionEditResource
+> There was no real distinction between them anymore since the core 2.0 update.
+> You can now use the base ItemResource and CollectionResource types instead
+
+## 2.4.0
+- Update Typescript version to `3.7.2`, also update other plugins 
+
+## 2.3.0
+- Add callbacks when errors are set/cleared to `TransactionEventHandler`
+- Added the possibility to differentiate between errors to display below a field and on the save button in `TransactionValidator`
+- Changed the format of the error translations from `string` to `() => string` in `TransactionValidator`
+> Now the translation function will only be called when the error is actually set, not when it's cleared
+
+## 2.2.1
+- Fixed a bug where resolving derived values for new items (in `TransactionCache.applyChangesDelta`) would sometimes error
+
+## 2.2.0
+- `ChangesDelta.setItem(s)Created` will now accept incomplete input values
+> It will now fetch a template for you and process the items, so you no longer need to do that yourself
+
+## 2.1.2
+- Fixed a bug where deleted ItemEntries weren't picked up when detecting transaction changes
+
+## 2.1.1
+- Fixed a bug where an ItemEntry's errors wouldn't be deleted when the ItemEntry was deleted on a transaction
+
+## 2.1.0
+- Refactor `TransactionCache.getItemsByQuery` to check cached entries (just like a collection)
+- Add `TransactionValidator`, allow passing of a `TransactionValidatorFactory` to a transaction
+> You can use these validators to set errors using `setItemError` and `setGlobalError`
+- Fixed a bug where `TransactionItemHandler.cloneItemEntry` could only clone entry with changes on the target transaction.
+> It will not look for changes recursively on the transaction change
+
+## 2.0.19
+- Ensure all requestColumns for newly created ItemEntries from a template are available
+- Ensure derived values for newly created ItemEntries from a template are available
+
+## 2.0.18
+- Include read-only columns when detecting changes in TransactionItemHandler.processItemEntryChanges
+> Read-only columns shouldn't count as changes on the tab, but they should be taking into account when deciding whether or not to call `onChange`
+
+## 2.0.17
+- Fixed a bug where deleting an item that isn't in the transaction's item entry cache would result in an error
+- Fixed a bug where response columns weren't set for newly created local CollectionEntries
+- Fixed a bug where items weren't matched for newly created local CollectionEntries
+
+## 2.0.16
+- Fixed a bug where queries with a link to a local parent item weren't updated on save
+
+## 2.0.15
+- Cache ItemEntries that fit collections on the CollectionEntry's query instead of the CollectionEntry's id
+- Add a 'hint' to ChangesDeltas which allows skipping the extra request to validate `maybe` query matches
+- Create transaction changes for ItemEntry updates in the changesDelta if non exist yet when calling `TransactionCache.applyChangesDelta`
+> This allows you to update values on a transaction without having to fetch a resource for it by calling
+> `ChangesDelta.setItemUpdated()`
+
+## 2.0.14
+- Fixed reading of derived values in `getItemIdByColumn` when a ChangesDelta is passed  
+
+## 2.0.13
+- Fixed a bug where the incorrect fields where applied to the ChangesDelta in `TransactionItemHandler.cloneItemEntry`
+- A RequestBuffer's promise will now resolve after the ServerCache.processResponse promise is done, ensuring all values are present before continuing
+- Request columns for the request ItemType will now properly be taken into account in ServerCache.processResponse ensuring root columns are always properly set. (This is used to update derived values) 
+
+## 2.0.12
+- Fixed a bug where created changes weren't copied to the itemchanges
+- Only take readonly parent columns instead of all readonly columns in `ApiFormatter.hasChanges`
+- Fixed a bug where ItemEntry's where still in `ItemCache.entriesByEntryId` after clearing them
+
+## 2.0.11
+- Fixed a bug where changes weren't copied to the itemchanges
+- Fixed correct isCalledAfterApiSave values on calls to ServerCache.processResponse
+
+## 2.0.10
+- Construct `ColumnSet` with proper `requestColumns` when creating a `Template` with additional columns
+
+## 2.0.9
+- Properly process linked items from the template request in `TransactionItemHandler.createItems`
+
+## 2.0.8
+- Fixed a bug where not all fields where available even tough an ItemResource with specific columns was created
+
+## 2.0.7
+- Define abstract copyTransactionItemEntryChanges on ItemHandlerBase
+- Implement copyTransactionItemEntryChanges on TransactionItemHandler and ServerItemHandler
+- Fix AbstractCache/ServerCache/TransactionCache `getParent` function arguments
+> With the newly added arguments the function definitions didn't align anymore causing typescript errors
+> Even though the arguments aren't used in the `ServerCache` they're added in there
+
+## 2.0.6
+- Remove `ApiFormatter.lazyClone`
+> You can't lazily clone moment objects because the moment you wanted to clone could be changed in the time the getter isn't invoked, resulting in a different value
+
+- Create a copy of the child transaction's field instead of copying the object reference in `TransactionCache.applyChangeFromChild` and `ChangesProcessor.executeCreateRequest`
+> When writing to the object references you're changing multiple transactions at once, while this should be handled by applyCHangesFromParent
+
+## 2.0.5
+- Add `callOnAddWithInitialItems` option to `CollectionResourceOptions`
+> If `true` the `onAdd` callback will be called with the initial set of items
+
+
+## 2.0.4
+- Add `isCalledAfterSocketUpdate` to `onAdd`, `onRemove` and `onChange` callbacks
+> You can use this if a data change should only trigger an action when the user caused it himself 
+
+## 2.0.3
+- Fix `CollectionEditResource.removeItems`
+- Move `getCurrentCollectionEntryCache` and `getCurrentItemEntryCache` from `TransactionCache` to `AbstractCache`
+
+## 2.0.2
+- Fix marking entries as deleted and compiling this into a request
+
+## 2.0.1
+- Expand CollectionEntry's columns in `ServerCollectionHandler.fetchCollectionData`
+
+## 2.0.0 - Major caching refactor
+- Completely reworked internal caching structure, see [this Confluence page](https://rentman.atlassian.net/wiki/spaces/DEV/pages/704872456/) for the motivations behind it.
+
+
+## 1.9.0
+- Don't create ItemResources when not returning links in `ItemAdministrator.getNewResourceWithId` and in `ItemAdministrator.constructOnItemsExpanded` 
+
+## 1.8.0
+- Remove `ResourceCache` and `resourceLevel`
+> You should now manually call `resource.clearResource` when you no longer need a resource
+- Add `onConstruct` function to `ItemResource` and `CollectionResource`
+> This is overwritten by the frontend to track resource creation
+
+## 1.7.6
+- Add priority parameter to local cache callbacks. The callback condition (`always` / `onClose` / `skipOnClose`) no longer has any effect on the order in which the callbacks get executed.
+- **Breaking:** Remove `LocalCacheCallbackCondition` enum.
+- Add `itemId` parameter to `ItemHandler.fetchNewItem`. An error is thrown when an ID already exists.  Add `getNewResourceWithId` to ItemAdministrator. Deprecate `getItemByState`.
+
+## 1.7.5
+- For template column sets it is no longer assumed all columns are present. This fixes an issue with incomplete column
+sets in the front-end.
+- Fix issue where `changesProcessor` instance was undefined in `itemResourceFactory` and `collectionResourceFactory`.
+Create variables for each core service in order to get a TypeScript error when a dependency hasn't been initialized yet.
+
+## 1.7.4
+- Add support for strict ItemType type checking in `FieldMap` 
+
+## 1.7.3
+- Add support for strict ItemType type checking
+> This is temporarily defaulted to `any` to prevent compile errors in the frontend 
+
+## 1.7.2
+- Fix some typing issues in:
+    - ApiResponseProcessor
+    - ItemCache
+    - KeyService 
+
+## 1.7.1
+- Fix issue where `CreateRequestFactory` would be undefined in `ChangesProcessor`.
+
+## 1.7.0
+- **Breaking:** remove `ChangesProcessorFactory`. Add `ChangesProcessor` instance to core directly. 
+
+### Resource caching
+- **Breaking:** the following properties are removed:
+    - On `ItemEntry`: `clearResources`, `deactivateResources`.
+    - On `CollectionEntry`: `clearResources`, `getCurrentResource`.
+    - On `CollectionResourceOptions`: `clearOnTabChange`, `clearOnSubTabChange`.
+- An additional `level` parameter has been added to all methods that return resources. 
+- When creating resources using `ItemResourceFactory` or `CollectionResourceFactory`, this parameter is mandatory.
+A `defaultResourceLevel` parameter has been added to the `LocalCache` constructor.
+- A `clearResources` method has been added to `ItemAdministrator`. When calling this method, all item / collection
+and collection resources with a level of `level` or higher will be removed.  
+- The `clearResources` method has been removed from `LocalCache`.
+- The `setCurrentLocalCache` function has been removed from `LocalCacheManagerInterface`.
+
+## 1.6.13
+- When encountering a collection entry with `PROMISED_EXPAND` status, call `getCachedEntryStatus` after the initial
+promise has been resolved.
+
+> This is the likely cause of the issue where `_resolve` is called on a non-deferred collection entry.
+
+## 1.6.12
+- Fix error that occurs when trying to resolve a non-deferred collection entry.
+
+## 1.6.11
+- Fix issue where `QueryMatcher.matchComplexQuery` would return the wrong value.
+
+## 1.6.10
+- **Breaking**: Remove `linkType`, `linkIdArray` properties from `LinkCollectionDefinition`. Add `linkType`,
+`linkIdArray` parameters to `ItemAdministrator.getLinkCollectionsFromDef`.
+
+## 1.6.9
+- Redeploy of `1.6.8`
+
+## 1.6.8
+- Add support for `not` in queries
+
+## 1.6.7
+- Fix issue where `CollectionMatcher.addToCollections` wouldn't return the correct type.
+
+## 1.6.6
+- Add `callOnAdd` parameter in `CollectionHandler.batchExtend`. Set `updateInitial` to true. Remove `updateInitial` parameter in `CollectionEntry.extend`, as it should always be true.
+> The `extend` function only concerns itself with remote items, so no local changes should be generated.
+
+## 1.6.5
+- Fix issue where a derived column could be marked as the `link` (parent) column in the column set.
+> This could lead to instances where a different column would be set to the value of the parent.
+
+## 1.6.4
+- Fix issue where the `onChange` collection callback would not be called when updating it in the options.
+- Add `callOnAdd` parameter to collection matcher. When set to `false`, `onAdd` is not called for the `resultCollectionResource`.
+
+## 1.6.3
+- Properly type ApiResponseProcessor - fetchObjectArray
+
+## 1.6.2
+- Fix issue where the collection handler would return collection entries before they were resolved when calling `batchFetch`.
+
+## 1.6.1-3
+- Check for linkedTo before checking for subqueries in QueryMatcher
+> Linkedto also has `.query` and was incorrectly marked as a subquery 
+
+## 1.6.1-2
+- Fixed shorthand query with null values
+> The QueryParser would incorrectly identify subqueries when using null in a shorthand
+
+## 1.6.1-1
+- Fixed shorthand query with Moment values
+> The QueryParser would incorrectly identify Moment objects as a subquery
+
+## 1.6.1
+- Added support for subqueries in QueryParser and QueryMatcher
+> Collections using subqueries will always return 'maybe' in the QueryMatcher
+
+## 1.6.0
+- All external callbacks are now wrapped in a `try ... catch` block. This prevents them from breaking core functionality. 
+- **Breaking**: Add `ExceptionHandlerInterface` parameter to core constructor. 
+
+## 1.5.9
+- Fix issue that occurs when trying to resolve a `ColumnSet` using a single non-existing column.
+Catch exceptions that might occur when resolving an `ItemEntry`.
+- Add `mergeRequestColumns`, `mergeResponseColumns` to `ColumnSet`. When encountering new items while expanding a collection, add them to the collection.
+
+## 1.5.8
+- Introduce `RemoteViewResource` and `LocalViewResource`.
+> The `fields` property of a `RemoteViewResource` represents
+server values, while the `fields` property of a `LocalViewResource` represents local values.
+- The `fields` property of a `ViewResource` is now read only.
+
+## 1.5.7-1
+- Make ItemResource/CollectionResource base class abstract
+- Add missing overload functions in some places
+- Fix default comparator `QueryMatcher.parseSimpleQuery`
+- Fix `ExtendedCollectionMatchResult` `collection` property type 
+
+## 1.5.7
+- Properly type Collections & ItemResources (and return values) in the whole core.
+> The core will now properly return Collections & ItemResources based on the passed CollectionOptions.
+> You can now also type the expected collection type
+
+``` 
+// Expects a collection with editCollection and editItems both `true`
+// Will properly return EditResources for all collection functions
+const collection: CollectionEditResource<EditResource>;
+
+// other variations are:
+// CollectionViewResource<ViewResource>
+// CollectionViewResource<EditResource>
+// CollectionEditResource<ViewResource>
+
+this.core.itemAdministrator.getCollection(
+	'Notitie',
+	{
+		editCollection: true, // Will return a CollectionEditResource 
+		editItems: true // Will return EditResources instead of ViewResources in `.items`
+	}
+)
+```
+
+## 1.5.6
+- Add `getAllLocalCaches` to `LocalCacheManagerInterface`, remove item entries from all local caches on socket delete.
+
+## 1.5.5
+- Add 'order' column type handling to ApiFormatter functions
+
+## 1.5.4
+- Fix issue where parent would be incorrectly set when cloning a single item.
+- Type functions related to expansion maps in `ItemEntryService`. 
+
+## 1.5.3
+- Fix issue where the `enableSave` collection resource option would default to `false`. This would throw an error when
+calling `save` on a collection resource where this option was not explicitly set. 
+
+## 1.5.2
+- Type functions in `ColumnUtil` class.
+- Add `getRequestColumnId` and `containsDerivedColumns` to `ColumnUtil`.
+> `getRequestColumnId` should be used instead of `Util.getFirstProperty` when retrieving a column ID.
+- **Breaking:** Remove `ColumnUtil.isColumnSubset`. Use `ColumnSet.isSuperSetOf` instead.
+- Remove `findColumnObject`. Rename `findColumn` to `findRequestColumn`. 
+
+## 1.5.1
+- Properly remove item entry stub from (local) cache when request fails.
+- Fix issue where item or collection options could be set to undefined.
+
+## 1.5.0
+- Add `SocketMessage` type and add types to `SocketMessageHandler`
+- Expand local items requested using `getItemById` or `getItemsById` in `ItemAdministrator`.
+(`fetchItem` or `fetchItems` in `ItemHandler`.)
+- Implement expanding of local collections. This no longer leads to invalid requests.
+- **Breaking:** The `expand` function in `CollectionEntry` now has an `ItemCache` parameter.
+- **Warning:** This version contains major changes.
+
+### Introduce typing of item and collection options
+- **Breaking:** Removed `QueryItemType` collection entry option.
+- **Breaking:** Removed `ItemResourceService`. 
+- Removed `processOptions` parameter from `createCollectionResource` (`ItemAdministrator`). It is now equivalent to
+`addCollection`.
+- When creating an item resource using `ItemResourceFactory`, a collection entry using `CollectionResourceFactory` or a
+collection resource using `CollectionResourceFactory` it is no longer necessary to process options beforehand. It is
+still necessary when interacting with `CollectionHandler` or `ItemHandler` directly.
+
+## v1.4.0
+- Add `expandProcessLinkedItems` and `expandAddToCollections` to `ItemAdministrator`. These are analogues to
+`processLinkedItems` and `addToCollections`, but also expand the items with (derived) values and columns as necessary.
+They have a slightly different type signature.
+- Whenever a collection is requested, the `CollectionHandler` now makes sure that added local items are expanded as
+necessary.  
+- **Breaking:** Last parameter of `ItemHandler.createLocalEntries` is now a callback function.
+- **Breaking:** Rename `TemplateLinkedItemEntryMap` type to `TemplateItemEntryMap`.
+
+## v1.3.8
+- Add `isSaving` to `LocalCache`
+> We use this to disable the cancel/save buttons while the localCache is saving in the frontend
+
+## v1.3.7
+- Fix issues that generate invalid requests / changes when moving existing item to another collection, then deleting the parent.
+- Remove slip workarounds
+- Add api request types
+- Add types to `ModuleChangesCompilation`
+
+## v1.3.6
+- Skip add / remove collection callbacks when calling `revertChanges` (`LocalCache`).
+
+## v1.3.5
+- Fix issue where items added to collections when resolving wouldn't be removed in `revertChanges` (`LocalCache`).
+
+## v1.3.4
+- Add country to isFilteredColumn in ColumnUtil
+
+## v1.3.3
+- Move processLocalConfigColumns and consolidateColumns from ColumnUtil to frontend
+> These functions are specifically used for rendering ui-grid in the frontend, so there's 
+no reason to have them in the core
+
+## v1.3.2
+- Fix types path in package.json
+
+## v1.3.1
+- Fix types path in package.json
+
+## v1.3.0
+- Rename PromiseInterface to PromiseLibraryInterface
+> PromiseInterface is now used for the internal promise type
+
+- Use PromiseInterface instead of Promise as internal promise type
+> This allows us to overwrite the PromiseInterface definition in the frontend indicate usage of ng.IPromise
+
+## v1.2.9
+- Call processOptions in fetchDerivedValuesByColumn
+> Bug was introduced earlier but got enabled in v1.2.7
+
+## v1.2.8
+- Add toJSON methods for ItemResources, ItemEntries, and ColumnSets to fix circular dependencies in JSON.stringify
+
+## v1.2.7
+- Set itemEntry parent when generating a stub
+
+## v1.2.6
+- Fix an issue introduced in v1.2.5.
+
+## v1.2.5
+- When a local item cannot by found, return a newly created item in `getItemByState` (`ItemAdministrator`) only. This
+solves an issue with refreshing on a local edit view.
+
+## v1.2.4
+- **Breaking:** When a local item cannot by found, instead of a new item being created an error is thrown. This means it
+is no longer possible to create local items using `getItemById` or `getItemsById` in the `ItemAdministrator` class.
+- **Breaking:** Removed `getItemDefinition` and `getItemByDef` in the `ItemAdministrator` class. Added `getItemByState`.
+- Renamed types `TemplateResponseItemEntryMap` to `TemplateItemEntryMap` and `TemplateResponseLinkedItemEntryMap` to
+`TemplateLinkedItemEntryMap`.
+- Removed `getCollectionCacheKey` in `KeyService`. (Legacy code.)
+
+## v1.2.3
+- Fixed issue where derived values deeper than one layer couldn't be resolved.
+
+## v1.2.2
+- Fixed issue where in derived values weren't set after create request.
+
+## v1.2.1
+- **Breaking:** Replaced the `initial` parameter with the `callOnChange` parameter (`true` by default) in the `commit`
+function of the `EditResource` class.
+- Fixed issue in `setLocalFields` (`ItemEntry`) where some values were wrongly assumed to be present in `initialValues`.
+- Optimization: Disabled automatic resolution of derived values in `addItems` (`CollectionEditResource`) when `modInstant` is set to true.
+
+## v1.2.0
+- **Breaking:** When calling `addItems` or `addItem` on the `CollectionEditResource` class derived values are now
+resolved automatically. Instead of a compound object like `{fields: {key: 'value'}, derived: {}}` an object like
+`{key: 'value'}` should now be used as argument when calling these functions.
+- **Breaking:** Added `localCache` parameter to `CollectionResource` constructor.
+
+## v1.1.20
+- Fixed minor issue where collection wouldn't be deferred properly before expanding.
+- `onChange` is now called automatically when when calling `commit` on an edit resource. 
+
+## v1.1.19
+- **Breaking:** Renamed `getCurrentChanges` to `getModuleChanges` in the `ItemAdministrator` class. Added optional
+`localCache` parameter.
+
+### Local cache callback refactoring
+- Removed `onSaveWithoutClosing` event.
+- Added `condition` parameter to `onBeforeSave` and `onSaveSuccess` (possible values are `always`, `onClose` or
+`skipOnClose`, defaults to `always`). Callbacks registered with `condition: always` will get executed before other
+callbacks.
+- Pass the local cache itself to all registered callback functions. Pass the item ID conversion map as second argument
+to `onSaveSuccess` callback functions.
+
+## v1.1.18
+- Calling `expand` on a `CollectionEntry` manually no longer defers the collection entry.
+- The `batchFetch` and `batchExpand` functions in the `CollectionHandler` class now properly defer and resolve the
+collection entries.
+
+## v1.1.17
+- Fixed issue where the `getLocalByQuery` function in the `ItemCache` class wouldn't return any items.
+- When batch resolving collection entries, `CollectionHandler` now looks for matching items using `getByQuery` instead
+of `getByParent`.
+
+### Cache invalidation
+- Added `queueReload` function to `ItemEntry` class. This will reload the item when the item entry itself or a
+collection entry containing the item is requested.
+- The `queueReload` function in the `CollectionEntry` class no longer directly defers the item.
+- Added `invalidateCache` function to the `ItemAdministrator` class. This will call `queueReload` on all item entries
+and collection entries.
+
+### Item entry refactoring
+- Renamed `process` to `setFields`. 
+- Replaced `processLocal` with `setLocalFields`. This function no longer has a `modified` parameter.
+- `setModified` now also sets local default values.
+- Removed `setCreator`. This function was called twice in some instances.
+- **Breaking:** Added `derived` parameter to `updateFields`  
+
+##v1.16
+- Pass `hasChanges` as second argument to `onBeforeSave` callbacks in  the `LocalCache` class. This fixes an issue with
+project financial values in the front-end. [RM4-9577]
+- Added `callOnActivate` parameter to `addItems` function in `CollectionEditResource` class. Use this to prevent items
+from being added to the local cache.  
+
+##v1.15
+- Fix `fetchItemTypesTranslations` function in `ColumnHandler` class.
+- Fix type definition of `PromiseInterface.all`.
+
+##v1.14
+- The `ChangesCompiler` now always processes local collections. (Even if they don't have edit resources.) This fixes an
+issue with recurring appointments in the front-end.
+
+##v1.13
+- Add option to exclude itemTypes during createLocalEntries.
+
+##v1.12
+- **Breaking:** `ItemResource.isNew` returns true *only* if the resource was created using 
+`ItemAdministrator.getNewResource` or `ItemAdministrator.getItemByDef`. This fixes an issue where items where removed
+from the local cache inadvertently.
+- The `start`, `commit` and `rollback` functions of `EditResource` now return the resource itself to facilitate chaining.
+- When calling `CollectionEntry.revertChanges`, callbacks like `onAdd` / `onRemove` and `onActivate` / `onDeactivate`
+are now respected. This fixes an issue where items where *not* removed from the local cache.
+- When removing *local* items from collections, they are removed from `initial` as well as `modified`. This fixes an
+issue where changes were being detected continuously.
+- Updated the order of requests in `changesProcessor`. The `update` request is now executed before the `delete` request,
+except when updating documents. This fixes several issues.
+- `CollectionCache` now uses a map instead of an array to store collections. This fixes an issue where the same
+collection was added multiple times.
+- Updated all models to use dependency objects. This increases ease of debugging.
+
+##v.1.11
+- Fixed issue that occurs when saving when having an existing item refer to a newly created item.
+- **Breaking:** Removed `ItemResourceService.isNewResource`.
+- **Breaking:** Renamed `ItemResource.isNewResource` to `ItemResource.isNew`. Removed parameter.
+- `ItemResource.isNew` is equivalent to `ItemResource.isLocal`, while `EditResource.isNew` checks also checks for
+ completed transactions. 
+
+##v.1.10
+- Fixed issue where changes on different subtabs were not detected.
+
+##v1.1.9
+- Exposed `noop` function on `RmCore` class.
+> This is used in order to check whether a callback has a default value. 
+- Added `copyRequestColumns` function to `ColumnUtil` class.
+- Made parameters of `ItemAdministrator.saveCurrentLocalCache` and `LocalCache.save` optional.
+- **Breaking:** Reordered parameters of `ChangesProcessor.execute` to be consistent with
+`ItemAdministrator.saveCurrentLocalCache`. The new order is `singleItems` - `collections` - `parameters` -
+`breakUpByParent` - `onAfterCreateCallback`.
+
+##v1.1.8
+- Set default value for `params` to `{filter: false}` in `request` function in `ColumnHandler` class.
+
+##v1.1.7
+- Fixed issue where cached item entries or collection entries wouldn't be added to the local cache.
+
+##v1.1.6
+- Fixed issue with deferred item entries.
+- Re-enable changes watcher after save.
+- Added optional `id` parameter to `LocalCache` constructor.
+
+##v1.1.5
+- Added `clearItem` function to `LocalCache` class.
+
+##v.1.1.4
+- Fix issue where items where not added to the local cache automatically when they where added to a collection.
+> This depends on the `callOnActivate` parameter. I've added this mainly because extending collections should *not* add
+the items to the local cache.
+> In other instances this might be debatable because it doesn't do any real harm. *Not*
+doing it however can definitely be harmful. 
+
+##v.1.1.3
+- Fixed an issue where all collections in a local cache would be cleared.
+- **Breaking:** Renamed `getCacheManager` to `getCurrentLocalCache` and `setCacheManager` to `setCurrentLocalCache` in
+`LocalCacheManagerInterface`.
+
+##v1.1.2
+- Fixed an issue concerning derived values.
+
+## v1.1.1
+- Fixed an issue where changes wouldn't be detected.
+- **Breaking:** Removed the `_hasChanges` function in the `localCache` class. If you want to force changes detection,
+call `detectChanges` instead. Otherwise, rely on the `hasChanges` variable.
+- **Breaking:** Removed the `enableWatcher` and `disableWatcher` functions. Use `enableChangesWatcher` and
+`disableChangesWatcher` instead.  
+
+## v1.1.0
+### Development
+
+#### Strict TypeScript compilation
+Added the following TypeScript compiler options:
+- noImplicitThis
+- noImplicitReturns
+- strictNullChecks
+- noUnusedLocals
+- noUnusedParameters
+
+I would advise enabling these for all TypeScript projects from now on.
+
+#### Ordered imports and dependencies
+Imports are now ordered alphabetically and grouped by folder. Added a TSLint option to enforce this.
+Please note that this also applies for imports from the folder the file is currently in.
+For example, in `models/ItemResource.ts`, `itemEntry` should be imported like so:
+`import { ItemEntry } from '../models';`
+
+Also, factory and class dependencies should be ordered alphabetically as well. This will make it easier to add and
+remove dependencies in the future.
+
+### Breaking changes
+
+- Renamed `changesCompiler` to `changesCompilation`, `changesCompilerFactory` to `changesCompilationFactory`,
+`moduleChangesCompiler` to `moduleChangesCompilation` and `moduleChangesCompilerFactory` to
+`moduleChangesCompilationFactory`.
+- Removed the `allLinks` parameter from the `query` function definition in the `ApiRequestServiceInterface`. This is
+no longer supported in the back-end.
+
+#### Item and collection entries
+- Moved *all* functions that handle item entries from the `ItemEntryService` to the `ItemEntry` class.
+- Added the following functions to `ItemEntryService`:
+	- `createLocalConversionMap`;
+	- `expandLocalConversionMap`;
+	- `expandConversionMap`;
+	- `batchExpandConversionMap`;
+	- `batchClone`.
+- Cloning of item entries now works slightly differently. The function will attempt to generate a new
+item ID, and update the conversion map accordingly, but will respect the item ID that is already there.
+
+#### Rework item caching
+Newly created item entries and collection entries are no longer added to the global *or* local cache by default. 
+All entries are added to the global cache on save. Item entries are added to the local cache when resources are created 
+using the item administrator or when resources are created when adding the items to a collection.
+
+> This will increase reliability by ensuring the global cache is no longer 'polluted' with local items. Also, this will
+> allow for the creation item and collection entries without caching them directly. This is required for the copying and
+> pasting of items.
+ 
+Other changes: 
+ 
+- Moved `saveLocal` to `ItemAdministrator`;
+- `ItemAdministrator.fetchTitle` should now be called instead of `ItemHandler.fetchTitle`;
+- The `ItemAdministrator` collection matching functions (`addToCollections`, `removeFromCollections`) should now be
+called instead of those in the `CollectionHandler`. The `CollectionHandler` should only be used to reflect changes
+already on the backend. (Use `getCollectionMatcher`.)
+
+
+##v1.0.33
+- Really fix types path
+
+##v1.0.33
+- Fix types path
+
+##v1.0.32
+- Update `tsconfig.json` to put definitions in the root folder
+> The app had an issue with AOT compilation because of this
+
+##v1.0.31
+- Fix `columnHandler.fetchItemTypeTranslations`
+> It incorrectly looped over the response map, it should now work again
+
+##v1.0.30
+- Remove `updateTabParams` from LocalCacheManagerInterface
+> The function wasn't used
+
+- Reworked class export
+> Imports are now done from @rentman/rm-core, old imports are broken. This is because the old export structure didn't always work
+
+##v1.0.29
+- Fix inverted inArray check in CollectionEntry.removeItems
+> A delete message from the socket deleted all BUT the deleted items, this should now be fixed
+
+##v1.0.28
+Bug fixes only
+
+##v1.0.27
+- `ItemEntry.initial` is now undefined by default
+> In the SocketMessageHandler we use this check to see if an ItemEntry is a stub 
+
+##v1.0.26
+Bundle both minified and unminified code, include sourcemaps from dev build
+
+##v1.0.24, v1.0.25
+! Use version `v1.0.26` !
+
+- The core now expects a `promiseInterface` that should implement the provided `promiseInterface`
+> We need to be able to hook into the promises in order to call a digest cycle to update the ui in the frontend
+
+- Rename `ItemEntry.entryId` to `ItemEntry.id
+> It used to be called `id`, but it was changed in the seperation of the core.
+> You can use the `id` to uniquely identify an entry, since itemId can be updated (local to saved id)
+
+- Rename ItemResource `startTransaction` to `start`
+> Other functions are called `commit` and `rollback` so having 'transaction' only for start doesn't make much sense
+
+- `SocketMessageHandler.onMessageReceived` now returns a promise
+> You can now use the updated items or hook into the result to update the ui for example
+
+
+##v1.0.23
+- Rename ResourceCache to LocalCache
+> LocalCache only caches local items (name better reflects functionality)
+
+- Remove getter/setter for hasChanges
+> hasChanges is called in a digest loop in the frontend, so for performance reasons we don't want to recompute the value every time
+ 
+- Remove `_getCollection` from ItemAdministrator
+> `_getCollection` is now named `getCollection` and the old `getCollection` is removed. The query is part of the
+> options and should not be given as a separate argument. This was included to support the frontend
+
+- Remove `saveCurrentTab` from ItemAdministrator
+> `saveCurrentTab` makes no sense because the core has no concept of tabs, you should use `saveCurrentLocalCache` instead
+
+- Remove `getTabEntry` and `resetTabEntry` from ItemAdministrator
+> `getTabEntry` and `resetTabEntry` make no sense because the core has no concept of tabs, you should use `getLocalCache` and `resetLocalCache` instead
+