Change access modifiers for futures month lookup collections #8028
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.
Description
This Pull Request modifies the access modifiers for the
_futuresMonthCodeLookup
and_futuresMonthLookup
collections, making them accessible from outside their containing class.Related Issue
N/A
Motivation and Context
The motivation behind this change is to allow access to these lookup collections from other classes or modules within the project. Currently, they are declared with the default access modifier, limiting their visibility to only within the containing class. By changing the access modifiers to public, other parts of the codebase can utilize these collections without needing to expose the entire containing class.
Requires Documentation Change
N/A
How Has This Been Tested?
This change has been tested locally by ensuring that other classes within the project can successfully access and utilize the _futuresMonthCodeLookup and _futuresMonthLookup collections after the access modifier modification. Unit tests covering the functionality of these collections have also been executed to verify that the changes do not introduce any regressions.
Types of changes
Checklist:
bug-<issue#>-<description>
orfeature-<issue#>-<description>