Updates for Svc/PrmDb corresponding to UT cmake update for protected/private (#3446)#3772
Merged
LeStarch merged 2 commits intonasa:develfrom Jun 25, 2025
Merged
Updates for Svc/PrmDb corresponding to UT cmake update for protected/private (#3446)#3772LeStarch merged 2 commits intonasa:develfrom
LeStarch merged 2 commits intonasa:develfrom
Conversation
Contributor
Author
|
@LeStarch From my initial poking, the updates to use UT_AUTO_HELPERS seems like it would require enough further re-work of the existing Testers that I think it would be worth making that its own issue/task. |
LeStarch
requested changes
Jun 21, 2025
| * requiring additional friendship declarations. It leverages the existing | ||
| * friendship between PrmDbImpl and PrmDbImplTester. | ||
| */ | ||
| class PrmDbImplTester { |
Collaborator
There was a problem hiding this comment.
Wasn't I expecting this to be renamed PrmDbTester? Or did I misunderstand?
Collaborator
There was a problem hiding this comment.
It looks like this may be entirely unused. Perhaps we can remove?
Contributor
Author
There was a problem hiding this comment.
We now have both PrmDbTester and PrmDbImplTester. (And what used to be PrmDbTester.cpp is now the TestMain file.)
PrmDbTesteris a friend ofPrmDbComponentBase- We use
PrmDbTesterto calldoDispatchwhich is declared private in PrmDbComponentBase (in PrmDbComponentAc.hpp) by doingthis->m_impl.doDispatch()from PrmDbTester
- We use
PrmDbImplTesteris a friend ofPrmDbImpl.- We use
PrmDbImplTesterto callclearDbwhich is declared private in PrmDbImpl (here) by doingthis->m_implTester.clearDb()from PrmDbTester. - We will get errors if trying to do
this->m_impl.clearDb()
- We use
Contributor
Author
|
I am going to move this back to draft to fix the naming inconsistencies. Will try to discuss with CogE on desired name and file pattern going forward. |
…private by updating driver name and updating PrmDbImplTester to PrmDbTester
LeStarch
approved these changes
Jun 25, 2025
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.
Change Description
I locally updated
fprime/cmake/settings.cmaketo change-DPROTECTED=protected -DPRIVATE=private. This causes additional build errors beyond all our updates in manual code for PRIVATE->private and PROTECTED->protected due to auto-coded files which use PRIVATE, PROTECTED. This set of changes is associated with fixingSvc/PrmDbso that the UTs in this directory can build and pass.Approach in this case was:
Rationale
#3446
Future Work
fprime/cmake/settings.cmakeitself - this will be done at the end<X>Implto<X>(separate issue)