WIP - Transition Public/Private classifications #2737
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
responsible for calling own data
scott062
changed the title
elizabeth-jimenez
previously approved these changes
Feb 26, 2024
elizabeth-jimenez
previously approved these changes
Feb 26, 2024
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.
Start of an idea to ensure the classifications component is always hydrated by the same data calls regardless of private vs public (and roles). This will help narrow down troubleshooting with PRD bug where the public version mismatches private
Client Profile Search - Unchanged but verify still works
Public Profile Page - Migrate to other EP
Private Profile Page - Unchanged, already using that EP
AI Research Pane - TBD