Release 3.0#1056
Merged
Merged
Conversation
- to basic use case reuse the same instance repository with cache
- now is not necessary using routes
- Remove getApi from InstanceRepository - Mark GetInstanceApiUseCase as deprecated for the future
Mapping attributes teis v40
…t_aggregated_data_exchange # Conflicts: # i18n/en.pot # i18n/es.po # i18n/fr.po # i18n/pt.po # src/domain/rules/entities/SynchronizationRule.ts
…ta_exchange Support for aggregated data exchange
…issue_instances # Conflicts: # i18n/en.pot # src/domain/instance/usecases/ListInstancesUseCase.ts
Only show instances with permission
…ation Incomplete cron expresion validation in scheduler
…ty_patches # Conflicts: # i18n/en.pot # package.json # yarn.lock
Apply security patches
…selection-and-download-payload # Conflicts: # i18n/en.pot # i18n/es.po # i18n/fr.po # i18n/pt.po # src/domain/synchronization/usecases/DownloadPayloadFromSyncRuleUseCase.ts
- Move the datastore parent-child selection algorithm from MetadataTable.handleTableChange into a standalone pure function computeDataStoreSelection in DataStoreSelectionUtils.ts. - Replace inline comments (Downward rule / Upward rule) with descriptive function names: propagateNamespaceSelection, findAffectedParents, recomputeNamespaceParents. - This makes the selection logic unit-testable without React dependencies and keeps handleTableChange as a thin orchestrator.
…teDataStoreSelection - Add tests for DataStoreMetadata.buildFromKeys covering valid input, excluded ids filtering, invalid format, empty input and namespace-only ids. - Add tests for isEmptyContent covering null, undefined, primitives, empty/non-empty objects and arrays. - Add tests for computeDataStoreSelection covering the four key scenarios: select namespace, deselect one key after namespace selection (the actual bug case), deselect namespace, and select individual key without namespace.
- Replace hardcoded "[NS]" literals in SummaryStep with DataStoreMetadata.NS_SEPARATOR and isNamespaceOnlySelected. - Fix counter in DataStore label to use summaryInfo.length instead of dataStoreInfo.length so the displayed count matches the visible items.
- Change mapDatastoreToDownloadItems to return error strings instead of throwing, matching the pattern used by mapToDownloadItems for regular metadata. Accumulate datastore errors alongside metadata errors. - Use error instanceof Error check to avoid interpolating [object Object] for non-Error throwables.
- Wrap "Key:", "All Keys" and "Namespace:" literals in SummaryStep with i18n.t() for consistency with the rest of the file.
…ownload-payload Datastore metadata sync does not reflect selected namespaces and keys correctly
…vents-sync-json # Conflicts: # i18n/en.pot # src/domain/synchronization/usecases/DownloadPayloadFromSyncRuleUseCase.ts
Program indicator sync succeeds but returns no data
…-excludes-metadata # Conflicts: # src/presentation/react/core/components/metadata-table/MetadataTable.tsx
[fix]: Preserve metadata selections when using "Select All" in metadata table
BundleMonNo change in files bundle size Groups updated (1)
Final result: ✅ View report in BundleMon website ➡️ |
TEI to DE wrong mapping
When replicating a rule, the wizard's initialization effect was calling setDefaultInclusions on the cloned rule, overwriting the source's sharing/users/orgUnits include-objects-and-references flags with the user's default inclusion config. The clone then ran without pulling those dependencies. Skip the defaults branch when a replicated rule is present in location.state.
fix: replicate rule inclusions
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📌 References
📝 Implementation
📹 Screenshots/Screen capture
🔥 Is there anything the reviewer should know to test it?
📑 Others
Any change in the GUI library? If so, what branch/PR?
Any change in the D2 Api? If so, what branch/PR?