Repository navigation
feat: support standard and custom dimensions in 1.1.0 - #1
Merged
Merged
Conversation
Preserve declared dimension names and voucher object references. Expose all discovered dimensions and allow analysis by standard name or number. Prepare version 1.1.0.
svenne87
approved these changes
Nov 6, 2026
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
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.
Support cost bearer, employee, customer, supplier and invoice dimensions alongside cost centers and projects. Other dimensions remain visible as integers and can be selected by SIE number.
Preserve DIM/UNDERDIM names and voucher object references, and discover dimensions from declarations, objects, period balances, budgets and transactions. Monthly reports still require period balances; transaction-only dimensions do not synthesize them.
Prepare release 1.1.0. Existing cost-center/project selectors remain supported. Consumers with closed dimension enums must extend their schemas before upgrading.
Validation: 47 examples passed, gem build succeeded, and diff whitespace checks passed.