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
* fix two way link removal processing.
* fix resolving two way link if target end doesnt exist. Previously it was marked as valid two way link
* changelog entry for bug fixes.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,11 @@
1
1
## 1.10.0
2
2
Release built: _not released yet_
3
3
4
+
### Bug fixes
5
+
- Fixed two bugs in two-way links returned from `/state/entity/details`:
6
+
- If one end of the link pointed to an entity without a corresponding metadata key, it was incorrectly considered a valid two-way link.
7
+
- Fixed invalidation after removing a metadata entry on one end. Previously, the link was still considered valid even after the metadata entry was removed.
8
+
4
9
### API Changes
5
10
- New filters are supported on the `/stream/transactions` endpoint:
6
11
-`transaction_status_filter` - Allows filtering by the transaction commit status (`Success`, `Failure`, `All`). Defaults to `All`.
@@ -36,7 +41,6 @@ Release built: _not released yet_
36
41
- Added a new configuration parameter, `GatewayApi__Endpoint__EntitiesByRoleRequirementLookupMaxRequestedRequirementsCount`, which sets the limit (default `50`) on the number of requirements that can be queried using the `/extensions/entities-by-role-requirement/lookup` endpoint.
37
42
- Added a new configuration parameter, `GatewayApi__Endpoint__ImplicitRequirementsLookupMaxRequestedRequirementsCount`, which sets the limit (default `100`) on the number of implicit requirements that can be queried using the `/extensions/implicit-requirements/lookup` endpoint.
0 commit comments