-
Notifications
You must be signed in to change notification settings - Fork 15
BC-11042 - Refactor collabora file dialog #3989
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
base: main
Are you sure you want to change the base?
Conversation
| it("should emit event", async () => { | ||
| const { wrapper } = await setup(); | ||
|
|
||
| const typeSelect = wrapper.findComponent(VSelect); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Das wäre eigentlich auch Setupfunktion im Szenario
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, ist das hier nicht "normales" test arrangement? bzw. was wäre denn die daumenregel bei uns, was wir ins setup packen? bei dem mocking und mock-return (dadrüber) bin ich bei dir - aber hier versteh ich das noch nicht ganz.
|



Short Description
Refactoring of the collabora file dialog to only have one feature dialog for usage in several places
Links to Ticket and related Pull-Requests
https://ticketsystem.dbildungscloud.de/browse/BC-11042
Changes
Data-security
Deployment
New Repos, NPM packages or vendor scripts
Screenshots of UI changes
Checklist before merging