Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New field to set 'coin:ss:idp_visible_only' #664

Merged
merged 6 commits into from
Sep 2, 2024
Merged

Conversation

MKodde
Copy link
Contributor

@MKodde MKodde commented Aug 6, 2024

The SAML and OIDC entities now allow for setting the coin:ss:idp_visible_only metadata setting. See the story for the fine details.

See: https://www.pivotaltracker.com/story/show/187515050

@MKodde MKodde requested a review from parijke August 6, 2024 10:01
@MKodde MKodde force-pushed the feature/visible-only branch 3 times, most recently from 45147df to 586ff59 Compare August 6, 2024 11:33
Copy link
Contributor

@parijke parijke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some suggestions

@@ -227,7 +227,9 @@ private function generateMetadataFields(ManageEntity $entity): array
if ($entity->getMetaData()->getLogo() instanceof Logo && $entity->getMetaData()->getLogo()->getUrl() !== '') {
$metadata = array_merge($metadata, $this->generateLogoMetadata($entity));
}

if ($entity->getMetaData()?->getCoin()->isIdpVisibleOnly() !== null) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does this mean? Tis is a fairly complex equation, and it is not clear what is meant. Using a descriptive method could maybe clarify a bit

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What part of the equation is complex in your opinion? I find it rather expressive, but I'm kind of biassed ;P

Copy link
Contributor

@parijke parijke Aug 29, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The whole part... I have no idea what true and false mean in this case. What means true here in 1 word?

@MKodde MKodde force-pushed the feature/visible-only branch 4 times, most recently from 6591958 to 076f04f Compare August 29, 2024 10:06
And carry them in on the Save commands
When editing an existing entity
The check would be type unspecific. That resulted in situations where "" would
be considered null. That resulted in the new coin value to never be set
for existing entities. As null would also evaluate to be true when the
new value for the value is `false`. As php thinks false == null when not testing
in a strict manner.
@MKodde MKodde merged commit 4acdb78 into main Sep 2, 2024
2 of 3 checks passed
@MKodde MKodde deleted the feature/visible-only branch September 2, 2024 07:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants