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

BC-8348 - Implement Sharing and Copying of Room Boards #3452

Open
wants to merge 25 commits into
base: main
Choose a base branch
from

Conversation

uidp
Copy link
Contributor

@uidp uidp commented Nov 14, 2024

Short Description

We have to implement sharing and copying of boards that are associated to rooms. Currently this is only possible for boards that belong to courses. In order to do this we have to extend the ShareTokenModule and BoardModule.

Links to Ticket and related Pull-Requests

BC-8348

Changes

Data-security

Deployment

New Repos, NPM packages or vendor scripts

Screenshots of UI changes

Checklist before merging

  • QA: In addition to review, the code has been manually tested (if manual testing is possible)
  • PO: Any deviation from requirements was agreed with Product-Owner / ticket author / support-team
  • DEV: Every new component is implemented having accessibility in mind (e.g. aria-label, role property)

Notice: Please keep this Pull-Request as a Draft (or add WIP label), until it is ready to be reviewed

@uidp uidp changed the title Bc 8348 copy share board Bc 8348 - Implement Sharing and Copying of Room Boards Nov 28, 2024
@@ -597,6 +597,10 @@ export default {
"components.molecules.import.columnBoard.options.selectCourse.infoText":
"Seleccione el curso al que desea importar el tablero.",
"components.molecules.import.courses.label": "Curso",
"components.molecules.import.columnBoard.options.selectRoom":
"Elija habitación",
Copy link
Contributor

Choose a reason for hiding this comment

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

We decided on going with "sala" instead of "habitación"

Copy link
Contributor Author

@uidp uidp Dec 2, 2024

Choose a reason for hiding this comment

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

Ok, can you help with the right translation? What would it be then - "Elija sala"?

role="menuitem"
data-testid="room-action-delete"
:aria-label="
$t('pages.roomDetails.ariaLabels.menu.action.delete')
"
@click="onDelete"
@click="deleteBoard"
Copy link
Contributor

Choose a reason for hiding this comment

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

A while ago we decided that "on" + eventName is our convention to name event handlers

Copy link
Contributor Author

@uidp uidp Dec 3, 2024

Choose a reason for hiding this comment

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

Ok, but it reads much better this way IMHO (like "At click: delete board"). And what about methods that are called from event handlers + from other methods? Should we wrap these methods in on<method> functions so they can be called as event handlers? Example would be createBoard which is called from fabItemClickHandler. Is there anything we gain in terms of readability when we prefix the event handlers with on?

@uidp uidp changed the title Bc 8348 - Implement Sharing and Copying of Room Boards BC-8348 - Implement Sharing and Copying of Room Boards Dec 2, 2024
Copy link

sonarcloud bot commented Dec 3, 2024

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