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
Copy file name to clipboardExpand all lines: CHANGELOG.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,14 @@
2
2
3
3
All changes that impact users of this module are documented in this file, in the [Common Changelog](https://common-changelog.org) format with some additional specifications defined in the CONTRIBUTING file. This codebase adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
4
4
5
+
## Unreleased [patch]
6
+
7
+
> Development of this release was supported by the [French Ministry for Foreign Affairs](https://www.diplomatie.gouv.fr/fr/politique-etrangere-de-la-france/diplomatie-numerique/) through its ministerial [State Startups incubator](https://beta.gouv.fr/startups/open-terms-archive.html) under the aegis of the Ambassador for Digital Affairs.
8
+
9
+
### Fixed
10
+
11
+
- Fix declarations validation when filters history is modified
12
+
5
13
## 7.2.2 - 2025-09-16
6
14
7
15
_Full changeset and discussions: [#1191](https://github.com/OpenTermsArchive/engine/pull/1191)._
@@ -47,7 +47,7 @@ export default class DeclarationUtils {
47
47
return;// Assuming history modifications imply corresponding changes in the service declaration and that the analysis of which terms types of this service have changed will be done when analysing the related declaration, no further action is required here
servicesTermsTypes[serviceId]=Object.keys(declaration.terms);// Considering how rarely filters are used, simply return all term types that could potentially be impacted to spare implementing a function change check
0 commit comments