Users/alkerezs/implement column descriptors #70
Merged
Conversation
This file contains 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
## [3.14.0](v3.13.0...v3.14.0) (2024-09-19) ### Features * **asset:** add calibration forecast property only row formatting ([#68](#68)) ([162d782](162d782))
kkerezsi
requested review from
CiprianAnton,
mure and
cameronwaterman
as code owners
saradei-ni
reviewed
Sep 30, 2024
CiprianAnton
approved these changes
Sep 30, 2024
src/datasources/asset-calibration/AssetCalibrationDataSource.test.ts
Outdated
Show resolved
Hide resolved
src/datasources/asset-calibration/AssetCalibrationDataSource.ts
Outdated
Show resolved
Hide resolved
saradei-ni
approved these changes
Sep 30, 2024
# Conflicts: # CHANGELOG.md
|
@mure I missed this. My bad . Will pay more attention to this on the next PRs |
|
🎉 This PR is included in version 3.14.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
Pull Request
🤨 Rationale
To have a more versatile naming strategy for the columns that allow replacing IDs with actual entity aliases, it is necessary to have a column descriptor defined on the FieldDTO for the Calibration Forecast.
👩💻 Implementation
🧪 Testing
✅ Checklist