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

feat: add new portal into runtime to include footer #9815

Merged
merged 1 commit into from
Oct 16, 2023

Conversation

LukasHirt
Copy link
Collaborator

@LukasHirt LukasHirt commented Oct 16, 2023

Description

Add a new portal into the application layout of runtime package. This portals allows developers to add new content below the app container. Because of this position, I chose the name footer for the portal. This change also makes the wrapper element of the container a flexbox. This is needed because the view itself has a limited height and this allows us to fit in the footer.

Related Issue

Motivation and Context

Enable adding new actions in the embed mode without touching the layout of files app.

How Has This Been Tested?

  • test environment: local dev env
  • test case 1: create a new element in files app and use portal to teleport it into the footer

Screenshots (if appropriate):

localhost_9200_files_spaces_personal_einstein_fileId=91b3fbd1-7964-4fbf-9d9c-0b94c6962fea%244c510ada-c86b-4815-8820-42cdf82c3d51%214c510ada-c86b-4815-8820-42cdf82c3d51 items-per-page=100 view-mode=resource-table tiles-size=1

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Technical debt
  • Tests

Checklist:

  • Code changes
  • Unit tests added
  • Acceptance tests added
  • Documentation ticket raised:

@update-docs
Copy link

update-docs bot commented Oct 16, 2023

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.

@LukasHirt LukasHirt force-pushed the feat/runtime-footer-portal branch from ec98161 to 4b62829 Compare October 16, 2023 14:41
@LukasHirt
Copy link
Collaborator Author

@JammingBen @dschmidt ping for review :)

If you have any hints/requirements about specific automated tests, please, let me know. Otherwise my plan is to do an E2E test in files app once the footer is implemented there to ensure the portal works...

@JammingBen
Copy link
Contributor

If you have any hints/requirements about specific automated tests, please, let me know. Otherwise my plan is to do an E2E test in files app once the footer is implemented there to ensure the portal works...

Actually we plan to have e2e tests for core functionality only. Hence I'd suggest not to worry about them - at least for now. Unit tests on the other hand are always welcome (though I don't know if it makes sense for a portal 😅 ).

Copy link
Contributor

@JammingBen JammingBen left a comment

Choose a reason for hiding this comment

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

LGTM 👍

Pipeline fails, looks flaky though. I restarted.

@LukasHirt
Copy link
Collaborator Author

Unit tests on the other hand are always welcome (though I don't know if it makes sense for a portal 😅 ).

I thinking about unit test but found this comment which kind of sounds discouraging...

LinusBorg/portal-vue#260 (comment)

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@JammingBen JammingBen merged commit e8caeb4 into owncloud:master Oct 16, 2023
2 checks passed
@LukasHirt LukasHirt deleted the feat/runtime-footer-portal branch October 16, 2023 17:28
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.

3 participants