fix: use isInline prop instead of isline-link styles #1542
+2
−2
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 PR updates the usage of the component in the Authn MFE to use the isInline prop instead of manually passing the "inline-link" class via className.
The isInline prop on the component defaults to false, which causes it to internally apply the standalone-link class in addition to any class passed through className. As a result, both inline-link and standalone-link classes were being applied simultaneously.
This conflict led to styling issues that caused the link to sometimes not render properly or appear invisible, especially in places where visual styling depends heavily on the correct class being applied.
The fix is to use the dedicated isInline prop so only one of the classes is applied
How Has This Been Tested?
Yes I have tested this with tutor local on my server
Screenshots/sandbox (optional):
Before

#After

Merge Checklist
Post-merge Checklist