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

fix: Fix displaying inaccessible application - MEED-7411 - Meeds-io/MIPs#156 #205

Merged
merged 1 commit into from
Sep 3, 2024

Conversation

boubaker
Copy link
Member

@boubaker boubaker commented Sep 3, 2024

Prior to this change, when adding a not accessible application inside a page using a dynamic container (with access permissions that the user is not member of), then a 'null' string is displayed instead of displaying an empty content. This change, ensures to not display the application at all and even hide the parent element to not have an additional padding.

…IPs#156

Prior to this change, when adding a not accessible application inside a page using a dynamic container (with access permissions that the user is not member of), then a 'null' string is displayed instead of displaying an empty content. This change, ensures to not display the application at all and even hide the parent element to not have an additional padding.
@boubaker boubaker merged commit fd3adbd into feature/whitepaper Sep 3, 2024
3 checks passed
@boubaker boubaker deleted the meed-7411 branch September 3, 2024 10:28
Copy link

sonarcloud bot commented Sep 3, 2024

exo-swf pushed a commit that referenced this pull request Sep 5, 2024
…IPs#156 (#205)

Prior to this change, when adding a not accessible application inside a
page using a dynamic container (with access permissions that the user is
not member of), then a 'null' string is displayed instead of displaying
an empty content. This change, ensures to not display the application at
all and even hide the parent element to not have an additional padding.
exo-swf pushed a commit that referenced this pull request Sep 5, 2024
…IPs#156 (#205)

Prior to this change, when adding a not accessible application inside a
page using a dynamic container (with access permissions that the user is
not member of), then a 'null' string is displayed instead of displaying
an empty content. This change, ensures to not display the application at
all and even hide the parent element to not have an additional padding.
boubaker added a commit that referenced this pull request Sep 5, 2024
…IPs#156 (#205)

Prior to this change, when adding a not accessible application inside a
page using a dynamic container (with access permissions that the user is
not member of), then a 'null' string is displayed instead of displaying
an empty content. This change, ensures to not display the application at
all and even hide the parent element to not have an additional padding.
boubaker added a commit that referenced this pull request Sep 5, 2024
…IPs#156 (#205)

Prior to this change, when adding a not accessible application inside a
page using a dynamic container (with access permissions that the user is
not member of), then a 'null' string is displayed instead of displaying
an empty content. This change, ensures to not display the application at
all and even hide the parent element to not have an additional padding.
boubaker added a commit that referenced this pull request Sep 5, 2024
…IPs#156 (#205)

Prior to this change, when adding a not accessible application inside a
page using a dynamic container (with access permissions that the user is
not member of), then a 'null' string is displayed instead of displaying
an empty content. This change, ensures to not display the application at
all and even hide the parent element to not have an additional padding.
boubaker added a commit that referenced this pull request Sep 5, 2024
…IPs#156 (#205)

Prior to this change, when adding a not accessible application inside a
page using a dynamic container (with access permissions that the user is
not member of), then a 'null' string is displayed instead of displaying
an empty content. This change, ensures to not display the application at
all and even hide the parent element to not have an additional padding.
boubaker added a commit that referenced this pull request Sep 5, 2024
…IPs#156 (#205)

Prior to this change, when adding a not accessible application inside a
page using a dynamic container (with access permissions that the user is
not member of), then a 'null' string is displayed instead of displaying
an empty content. This change, ensures to not display the application at
all and even hide the parent element to not have an additional padding.
exo-swf pushed a commit that referenced this pull request Sep 5, 2024
…IPs#156 (#205)

Prior to this change, when adding a not accessible application inside a
page using a dynamic container (with access permissions that the user is
not member of), then a 'null' string is displayed instead of displaying
an empty content. This change, ensures to not display the application at
all and even hide the parent element to not have an additional padding.
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.

1 participant