Resource discovery: Implement folder and resource card #12418

AllanOXDi · 2024-07-04T21:44:57Z

Summary

The PR introduces a new folder card to Kolibri to support of coach resource discovery . See #12318

Screen.Recording.2024-07-25.at.19.53.42.mov

References

Reviewer guidance

While reviewing this PR, please note that I have decided to leave out a few acceptance criteria requirements, namely support for RTL.

Please note that this was built on top of the KCard, which supports two layouts (i.e., vertical and horizontal) with their respective thumbnail display options and for folder cards, the thumbnail display area is currently shown on the left when the display is large. but it require it to be on the right when the thumbnailDisplay prop is set to 'large', in addition to the title prop taking up the position of the above title slot in these kinds of layouts. This is currently not covered by KCard.

Vs the design spec

After discussing with @MisRob, we decided to work with what KCard supports for this issue and file a follow-up issue on KDS to handle these edge cases.

I have made a minor stying adjustment to the below title slot on KCard . To test this PR you would need to work with this KDS PR learningequality/kolibri-design-system#688

Here are a few things to look at:

Does it have Folder titleF, icon , label and Folder thumbnail picture?
Folder thumbnail placeholder when a picture is not available?
Is it responsive ?

Testing checklist

Contributor has fully tested the PR manually
If there are any front-end changes, before/after screenshots are included
Critical user journeys are covered by Gherkin stories
Critical and brittle code paths are covered by unit tests

PR process

PR has the correct target branch and milestone
PR has 'needs review' or 'work-in-progress' label
If PR is ready for review, a reviewer has been added. (Don't use 'Assignees')
If this is an important user-facing change, PR or related issue has a 'changelog' label
If this includes an internal dependency change, a link to the diff is provided

Reviewer checklist

Automated test coverage is satisfactory
PR is fully functional
PR has been tested for accessibility regressions
External dependency files were updated if necessary (yarn and pip)
Documentation is updated
Contributor is in AUTHORS.md

github-actions · 2024-07-04T21:51:27Z

Build Artifacts

Asset type	Download link
PEX file	kolibri-0.17.0a0.dev0_git.251.gfe58625a.pex
Windows Installer (EXE)	kolibri-0.17.0a0.dev0+git.251.gfe58625a-windows-setup-unsigned.exe
Debian Package	kolibri_0.17.0a0.dev0+git.251.gfe58625a-0ubuntu1_all.deb
Mac Installer (DMG)	kolibri-0.17.0a0.dev0+git.251.gfe58625a.dmg
Android Package (APK)	kolibri-0.17.0a0.dev0+git.251.gfe58625a-0.1.4-debug.apk
TAR file	kolibri-0.17.0a0.dev0+git.251.gfe58625a.tar.gz
WHL file	kolibri-0.17.0a0.dev0+git.251.gfe58625a-py2.py3-none-any.whl

MisRob

Hi Allan, thanks :) I appreciate clarity in the PR description in regard to review and also what's done and what's coming, helpful. I hope to have all issues I promised to open ready soon. Cards look very good, and their API interface makes sense to me. I am leaving a couple of comments from the first code walkthrough.

MisRob · 2024-07-25T18:26:48Z

kolibri/plugins/coach/assets/src/views/plan/LessonResourceSelectionPage/ContentCardList.vue

@@ -37,7 +37,13 @@
          disabled, tabindex, is-leaf class set here to hack making the card not clickable
          if you're trying to make the card clickable remove these properties
        -->
+        <AccessibleFolderCard
+          v-if="content.kind === 'topic'"


Not so important as it's temporary change, rather just fyi for future work there's constants available here

kolibri/kolibri/core/assets/src/constants.js

Lines 28 to 42 in df0c4ee

export const ContentNodeKinds = {

AUDIO: 'audio',

DOCUMENT: 'document',

VIDEO: 'video',

EXERCISE: 'exercise',

TOPIC: 'topic',

HTML5: 'html5',

CHANNEL: 'channel', // e.g. a root topic

EXAM: 'exam',

LESSON: 'lesson',

CLASSROOM: 'CLASSROOM',

ACTIVITY: 'ACTIVITY',

SLIDESHOW: 'slideshow',

BOOKMARK: 'bookmark',

};

kolibri/plugins/coach/assets/src/views/plan/LessonResourceSelectionPage/ContentCardList.vue

kolibri/plugins/learn/assets/src/views/LibraryPage/AccessibleFolderCard.vue

MisRob · 2024-07-25T19:06:05Z

kolibri/plugins/learn/assets/src/views/LibraryPage/AccessibleFolderCard.vue

+      <KCard
+        class="card"
+        :to="to"
+        :headingLevel="2"


[required] I'd suggest that <AccessibleFolderCard> has a headingLevel prop and just passes its value to KCard via the same prop. Reason being that <AccessibleFolderCard> will be used from more pages in Kolibri, and on each page it can be a member of a different level. This will ensure that devs always make sure to configure it explicitly and correctly in the context of a given page.

MisRob · 2024-07-25T19:15:32Z

kolibri/plugins/learn/assets/src/views/LibraryPage/AccessibleFolderCard.vue

+      >
+        <template #thumbnailPlaceholder>
+          <div>
+            <CardThumbnail


[required] Regarding the usage of <CardThumbnail> here, KCard doesn't need to use another component to re-implement the whole thumbnail area because it already provides it. If we used <CardThumbnail> here, that would override everything in unintended ways, and it's also unnecessary extra work. Let's leave KCard to do everything it can and only put folder icon into the #thumbnailPlaceholder slot. I realize that the slot's name is not intuitive in this regard - can you think of a better name?

(side note for context, ultimately, a big future goal is to get rid of all current card components in Kolibri, <CardThumbnail> included, in favor of KCard)

kolibri/plugins/learn/assets/src/views/LibraryPage/AccessibleFolderCard.vue

AlexVelezLl

Thank you @AllanOXDi! Its super exciting to see KCard already being used in our codebase!! 🎉, and see that the initial implementation has covered the most usecases we had. I left just a couple of thoughts, mostly regarding the html semantic structure 🤗.

kolibri/plugins/coach/assets/src/views/plan/LessonResourceSelectionPage/ContentCardList.vue

kolibri/plugins/learn/assets/src/views/LibraryPage/AccessibleFolderCard.vue

marcellamaki

Hi @AllanOXDi thanks for the great work on this!

My main suggestion here is for this PR but also helps us with the "how do we move past a working branch into the 'mainline' work for 0.18 question".

We should move both the ResourceCard and the FolderCard to kolibri-common. This allows the work to be merged into develop with minimal additional changes, provides the cards for shared use, and also prevents cross-plugin imports (totally fine for this working branch and testing, but not something we want to merge into production. Why no cross-plugin imports? Since it's a plugin architecture, we cannot merge code that assumes the existence of another plugin. Each plugin shouldn't "know" about other plugins that exist, or depend on them. More questions? Richard would love to tell you about it).

Having this implementation as it is, and using the updated version in the content card list is very helpful for manual QA. So, after moving these new components into kolibri-common, please update the reference for the import in the ContentCardList for final QA and feedback, so we can make sure everything moved over well.

Once all of the feedback on the cards themselves is resolved, and we confirm with QA that the new cards work as expected in Coach in the ContentCardList with no regressions, I think we can retarget this PR to develop and merge it directly there. I will then update the related issues in the milestone to be follow up issues that build on top of this foundation. I'm going to think about whether or not we want to include the ContentCardList update, or if we just want to include the cards being available in kolibri-common with no actual "placement" of them yet. If anyone has pros/cons, please share.

Also, a bit of a nitpick, but let's have a consistent name for the new cards -- I think making sure it's Accessible_____Card for each makes sense, so update AccessibilityResourceCard to be AccessibleResourceCard.

Great work! I'm so excited that finally KCard in Kolibri is coming to life!!!! 🎉 🎉 🎉 🎉 🎉 It's been a long time coming, and past Marcella, who struggled through 0.15 card refactoring (and many patch release "fixes" on the card UI ever since), is very grateful!

kolibri/plugins/coach/assets/src/views/plan/LessonResourceSelectionPage/ContentCardList.vue

MisRob · 2024-08-28T04:23:16Z

@AllanOXDi After all feedback here is resolved, and also learningequality/kolibri-design-system#752 finished and linked here, please ping me here - will do one final read through and then we should be ready to develop merge.

kolibri/plugins/learn/assets/src/views/LibraryPage/AccessibilityResourceCard.vue

kolibri/plugins/learn/assets/src/views/LibraryPage/AccessibleFolderCard.vue

nucleogenesis

Overall things are looking good! Just a couple non-blocking code questions from me on code review. Great work Allan!

nucleogenesis · 2024-08-30T21:31:02Z

packages/kolibri-common/components/Cards/AccessibleFolderCard.vue

+    :to="to"
+    :headingLevel="headingLevel"
+    layout="horizontal"
+    thumbnailDisplay="large"
+    :title="contentNode.title"
+    :thumbnailSrc="thumbnailSrc"
+    thumbnailScaleType="centerInside"
+    thumbnailAlign="right"
+    :style="{ height: '172px', margin: '16px 0 16px 0' }"


Non-blocking question:

Would any of these other KCard props be good to accept as props in AccessibleFolderCard? Like - would we ever want to use this card in a context where we want a different thumbnail(Align|Display|ScaleType) or layout values?

Sorry I missed this comment but I get your point, according to @MisRob suggestion here #12418 (comment), states otherwise.

@nucleogenesis I am certain that scale type will always be the default centerInside in all card components because their thumbnails are user-uploaded and don't have consistent ratios (you can see more in KImg -> Usage > Scaling).

Regarding the layout related settings, each of the three cards has its layout configuration. As far as we know from the designs, we won't be using multiple configurations for the folder card I commented on, however I can imagine this could easily change depending on the future designs and card type (there's more layouts for the resource card, I believe).

So if it feels important to think through it more carefully, perhaps each prop deserves its own consideration.

In the comment you reference @AllanOXDi, I don't mean to suggest we never use these extra props, but rather that we start using them when there's an actual need. You could argue otherwise depending on a mental model for these cards. I emphasized simplicity at this point, but nothing blocking. You can take it as one of the perspectives on designing interfaces in general and welcome to choose which way to go.

But also at this point we won't be allowing a lot customization of these cards beyond the design. I do remember the reason as to why we allowed customization further using thumbnail(Align|Display) was handle the edge cases that these cards provide.

These make your point valid @MisRob. Keep it simple and wait until there is a need to

But also at this point we won't allowing a lot customization of these cards beyond the design.

Oh yes, that's true, I just wanted to also acknowledge I see your point in having some customizations. Even though I didn't observe this for the folder card where the discussion originated, later I realized more broadly there's more to it, for example the resource card will likely need to accept more layouts and thumbnailDisplays in close future :) I double-checked designs earlier today to think more about this and noticed

Anyways, good considerations here! You're welcome to put it together and arrive at something that makes most sense to you taking into account all these pieces.

nucleogenesis · 2024-08-30T21:32:12Z

packages/kolibri-common/components/Cards/AccessibleFolderCard.vue

+      thumbnailSrc: {
+        type: String,
+        default: null,
+      },


Non-blocking question:

Is this prop here so that we can override the content's thumbnail value? Is there an expected case of using anything besides contentNode.thumbnail for the thumbnail here?

Yes , the prop thumbnailSrc is to override the value of the KImg in the KCard. No I think the chances of using anything besides contentNode.thumbnail are very minimal

MisRob · 2024-09-04T19:50:30Z

packages/kolibri-common/components/Cards/AccessibleResourceCard.vue

@@ -0,0 +1,131 @@
+<template>
+
+  <div>


[required] Here let's remove this outer <div>. It's not needed, and more importantly AccesibleResourceCard/KCard as <li> will need to be a direct child of KCardGrid as <ul>

MisRob · 2024-09-04T19:55:31Z

packages/kolibri-common/components/Cards/AccessibleResourceCard.vue

+            :color="$themePalette.grey.v_600"
+            :ariaLabel="coreString('savedFromBookmarks')"
+            :tooltip="coreString('savedFromBookmarks')"
+            @click="$emit('toggleInfoPanel')"


Nice, I think at this point it makes sense for this card to just emit on action rather than to contain handling implementation.

[required] I think we will need to rename emitted event names though to something meaningful. For example just toggleBookmark and for the other emit on line 45 it could be toggleInfo? I think this should reflect these two icon buttons.

MisRob · 2024-09-04T19:59:04Z

packages/kolibri-common/components/Cards/AccessibleResourceCard.vue

+</script>
+
+
+<style lang="scss" scoped>


[required] Let's cleanup unused classes such as folder-header-bar and possibly others below as well.

MisRob · 2024-09-04T20:01:17Z

Couple of last notes from me @AllanOXDi, then I think we'll be ready for merge :)

AllanOXDi · 2024-09-04T20:18:02Z

Couple of last notes from me @AllanOXDi, then I think we'll be ready for merge :)

Done!

MisRob · 2024-09-04T20:18:29Z

I also manually tested the new resource card now and one thing came out it'd be good to address now and that is when I click the bookmark or info icon buttons, I'm redirected. The expected behavior is rather that the two events get emitted (as already implemented) but we're not redirected to the card's target. I think we already achieved this in Studio somehow?

Other than that I think both the folder card and resource card have all they should in the scope of this PR. Regarding a11y QA, as discussed we will do that as part of actual features when the card grid is introduced.

MisRob · 2024-09-10T15:35:04Z

@AllanOXDi following-up on ^

I assume that @click.stop like you did here should do? learningequality/studio@07a4131#diff-a836f27f6ada2a7aa18ebaa5c94993244781588b3be7930037c89960c3d556bdR34-R35

AllanOXDi · 2024-09-10T16:09:46Z

I assume that @click.stop like you did here should do? learningequality/studio@07a4131#diff-a836f27f6ada2a7aa18ebaa5c94993244781588b3be7930037c89960c3d556bdR34-R35

This is something that I already tried.

MisRob · 2024-09-11T08:18:48Z

This is something that I already tried.

@AllanOXDi would you say a bit more so I can understand what was troubling - best would be to share the concrete code updates. Would you open a trial branch from this one, pushed what you played around with, and shared the link? I can then preview what changes you actually did and help debug.

AllanOXDi · 2024-09-11T11:27:02Z

Let me do so

AllanOXDi · 2024-09-11T11:40:50Z

AllanOXDi#3

MisRob · 2024-09-11T12:17:53Z

Thank you @AllanOXDi, I will look at it later today if I can spot something :) As KCard went through many updates since, it's possible something works differently compared to the first Studio version.

MisRob · 2024-09-11T15:54:04Z

@AllanOXDi I looked into the issue with @click.stop not working and it's a regression I caused in KCard a couple of weeks ago. Fixed it here learningequality/kolibri-design-system#774. Would you try to link and confirmed it helps?

AllanOXDi · 2024-09-11T17:27:23Z

It's working fine- thanks for the fix

…rd, which is to navigate to a new route.

marcellamaki · 2024-09-12T18:01:28Z

Hi @MisRob @AllanOXDi - I have started my review here and have a few thoughts. I'll add some comments and questions tomorrow. Some of them are probably for follow up and some are more general questions as I get more familiar with the relationships between these cards and KCard. Overall it's looking really nice Allan, thanks for all of your hard work!

marcellamaki

Hi @AllanOXDi Thank you for the great work on this. I can really see your increased comfort with all thing Vue components and navigating between KDS components and custom components in our products! I added a couple of comments but they're small.

Aside from the comments, I wanted to raise a little feedback that is outside of the scope of this PR but is interesting for the sake of learning and planning around the mobile view of the cards and this project.

On mobile view of the Folder card, the layout is technically responsive, which is great, but you can see it's a bit crowded.

I realize that the screenshot included in the issue only had more of a "list" view and didn't clearly state that there would be different sizes on mobile. And the image preview in the issue didn't include the mobile level responsiveness specifically. When we actually use this card (beyond just what you have here for the demo), I think we'll want to make sure we use the version of KCard that is aligned with the spec..

From my understanding talking to @MisRob, it will be simple to do this with a different layout that exists, to be vertical vs. horizontal, which is already supported in KCard

You could try out doing this conditionally where the card is called

  <Accessible...Card layout=breakpointLevel === 0 ? "'vertical" : "'horizontal">

but only if you're curious to test it out and see for yourself, as this isn't the final usage and you will be removing that code before merge anyways :)

In upcoming work I'd also encourage you to use a critical/reflective eye when are playing around with testing, and raise questions like "does this look right? did we overlook a mobile display? does this seem like what the designer intended?" Again, this isn't strictly in scope for this PR as the current "use" of the card is for manual QA only. And it's not a criticism of the implementation, but rather some thoughts to help with broader context thinking beyond the checklist of acceptance criteria. Noticing and sharing your perspective on things early, even if it seems like something a bit outside of your task list, is always helpful, and it helps you continue to build those reflective/questioning skills 🙂 And practically speaking, it will also help us make sure we do things like share with the team some of these features of the new KCard and helps me remember to include these details in upcoming issues I'm writing.

marcellamaki · 2024-09-13T15:45:10Z

kolibri/plugins/coach/assets/src/views/plan/LessonResourceSelectionPage/ContentCardList.vue

@@ -225,4 +237,9 @@
    margin-left: $checkbox-offset;
  }

+  /deep/ .horizontal-with-large-thumbnail {
+    height: 141px;
+    margin: 0 0 16px;


I'm wondering why there's a need to use /deep/ here, and if this is because this is more of an MVP, rather than the full implementation, or if there's something that we're missing with the KCard API. To me this is a small thing but an indicator that something is not quite as flexible as it needs to be, or like we've missed a detail and now are overriding something where there might be a better approach.

This is a bit of a nitpick, but I'm also confused about why the height is 141 px specifically. Was it this in the spec? We usually stick with 4 or 8px increments, or at the very least an even number.

currently, KCard has no set hight and and width- it's something that will be implemented in the gird. So I was just trying to play around with the number to make sure I'm close tot the the design

I asked @AllanOXDi to not worry too much about these temporary files :) As mentioned this won't be configured on KCard at all and this whole file will be removed before we merge.

However, it's definitely relevant notes and good guidance. @AllanOXDi it may be be helpful to comment on things like this in the PR comments or code comments so reviewers who don't have context (or just people like me with bad memory :-) can understand things like this.

marcellamaki · 2024-09-13T15:45:24Z

kolibri/plugins/learn/assets/src/views/LibraryAndChannelBrowserMainContent.vue

@@ -25,6 +25,18 @@
        </template>
      </component>
    </component>
+
+    <h2>AccessibleResourceCard preview</h2>


Let's just make sure to remove this before merge

Okay. Once It's approve, I will remove it before merge. I wish I had added a comment

marcellamaki · 2024-09-13T15:47:11Z

packages/kolibri-common/components/Cards/AccessibleFolderCard.vue

+  >
+    <template #thumbnailPlaceholder>
+      <div class="default-folder-icon">
+        <KIcon


Not sure if I'm missing something with the KCard implementation itself, but it looks like this KIcon is always present. We do want to have it as the default, it should only appear if there is not a thumbnail. You can see most clearly on small screen.

I see. I will try and fix it asap

@marcellamaki @AllanOXDi for context, the placeholder element, here icon, is not displayed only when there is no thumbnail image but also while it's loading. This is a progressive loading experience, important particularly on slower networks.

The bug here is caused by KCard not detecting that the image has finished loading. I recently fixed this and it will be available in my upcoming KDS PR.

However @AllanOXDi on Kolibri side, it may be helpful to double-check how the icon looks like on smaller resolutions when the thumbnail image is not available. It shouldn't overflow the area in this way and Kolibri needs to configure this.

@AllanOXDi so you can just fix the icon placement and size here if needed, but please don't add any logic regarding whether it's present or no.

github-actions bot added APP: Learn Re: Learn App (content, quizzes, lessons, etc.) DEV: frontend labels Jul 4, 2024

AllanOXDi changed the title ~~introduce kcard to kolibri~~ Resource discovery: Implement folder card Jul 5, 2024

github-actions bot added the APP: Coach Re: Coach App (lessons, quizzes, groups, reports, etc.) label Jul 23, 2024

AllanOXDi changed the base branch from develop to release-v0.17.x July 23, 2024 22:10

AllanOXDi changed the base branch from release-v0.17.x to introduce-cards July 24, 2024 18:47

AllanOXDi force-pushed the accesibility-folder-card branch from d4b1a45 to 9bba53c Compare July 24, 2024 21:46

AllanOXDi requested review from nucleogenesis, MisRob and AlexVelezLl July 25, 2024 17:33

AllanOXDi marked this pull request as ready for review July 25, 2024 17:34

MisRob reviewed Jul 25, 2024

View reviewed changes

MisRob self-assigned this Jul 30, 2024

AlexVelezLl reviewed Aug 9, 2024

View reviewed changes

marcellamaki self-requested a review August 23, 2024 14:25

marcellamaki added this to the Kolibri 0.18: Coach Resource Discovery milestone Aug 27, 2024

marcellamaki requested changes Aug 27, 2024

View reviewed changes

kolibri/plugins/coach/assets/src/views/plan/LessonResourceSelectionPage/ContentCardList.vue Outdated Show resolved Hide resolved

MisRob changed the title ~~Resource discovery: Implement folder card~~ Resource discovery: Implement folder and resource card Aug 28, 2024

MisRob reviewed Aug 28, 2024

View reviewed changes

kolibri/plugins/learn/assets/src/views/LibraryPage/AccessibilityResourceCard.vue Outdated Show resolved Hide resolved

MisRob reviewed Aug 28, 2024

View reviewed changes

kolibri/plugins/learn/assets/src/views/LibraryPage/AccessibleFolderCard.vue Outdated Show resolved Hide resolved

MisRob reviewed Aug 28, 2024

View reviewed changes

kolibri/plugins/learn/assets/src/views/LibraryPage/AccessibleFolderCard.vue Outdated Show resolved Hide resolved

MisRob mentioned this pull request Aug 28, 2024

Resource discovery: Implement resource card #12319

Open

9 tasks

AllanOXDi force-pushed the accesibility-folder-card branch from 4a33906 to 50a4013 Compare August 29, 2024 20:16

github-actions bot added DEV: frontend DEV: tools Internal tooling for development labels Aug 30, 2024

AllanOXDi changed the base branch from introduce-cards to develop August 30, 2024 18:45

AllanOXDi changed the base branch from develop to introduce-cards August 30, 2024 18:48

AllanOXDi changed the base branch from introduce-cards to develop August 30, 2024 18:59

nucleogenesis reviewed Aug 30, 2024

View reviewed changes

minor cleanup

2cd2cd8

MisRob reviewed Sep 4, 2024

View reviewed changes

MisRob requested a review from marcellamaki September 4, 2024 20:04

code clean up

a59a286

AllanOXDi force-pushed the accesibility-folder-card branch from fe1fd87 to a59a286 Compare September 4, 2024 20:17

MisRob mentioned this pull request Sep 11, 2024

KCardGrid: Part 1 - Prepare KCard + few bugfixes and a visual spacing update learningequality/kolibri-design-system#774

Merged

8 tasks

add click.stop on the buton to preventthe default behavior of the ca…

d71bb85

…rd, which is to navigate to a new route.

AllanOXDi force-pushed the accesibility-folder-card branch from 6f9b648 to d71bb85 Compare September 11, 2024 17:33

[pre-commit.ci lite] apply automatic fixes

56e7225

marcellamaki reviewed Sep 13, 2024

View reviewed changes

	export const ContentNodeKinds = {
	AUDIO: 'audio',
	DOCUMENT: 'document',
	VIDEO: 'video',
	EXERCISE: 'exercise',
	TOPIC: 'topic',
	HTML5: 'html5',
	CHANNEL: 'channel', // e.g. a root topic
	EXAM: 'exam',
	LESSON: 'lesson',
	CLASSROOM: 'CLASSROOM',
	ACTIVITY: 'ACTIVITY',
	SLIDESHOW: 'slideshow',
	BOOKMARK: 'bookmark',
	};

		</script>


		<style lang="scss" scoped>

Resource discovery: Implement folder and resource card #12418

Are you sure you want to change the base?

Resource discovery: Implement folder and resource card #12418

Conversation

AllanOXDi commented Jul 4, 2024 • edited Loading

Summary

References

Reviewer guidance

Testing checklist

PR process

Reviewer checklist

github-actions bot commented Jul 4, 2024 • edited Loading

MisRob left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

AlexVelezLl left a comment

Choose a reason for hiding this comment

marcellamaki left a comment • edited Loading

Choose a reason for hiding this comment

MisRob commented Aug 28, 2024

nucleogenesis left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

AllanOXDi Sep 4, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

MisRob Sep 4, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

MisRob commented Sep 4, 2024

AllanOXDi commented Sep 4, 2024

MisRob commented Sep 4, 2024

MisRob commented Sep 10, 2024

AllanOXDi commented Sep 10, 2024

MisRob commented Sep 11, 2024

AllanOXDi commented Sep 11, 2024

AllanOXDi commented Sep 11, 2024

MisRob commented Sep 11, 2024

MisRob commented Sep 11, 2024 • edited Loading

AllanOXDi commented Sep 11, 2024

marcellamaki commented Sep 12, 2024

marcellamaki left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

AllanOXDi commented Jul 4, 2024 •

edited

Loading

github-actions bot commented Jul 4, 2024 •

edited

Loading

marcellamaki left a comment •

edited

Loading

AllanOXDi Sep 4, 2024 •

edited

Loading

MisRob Sep 4, 2024 •

edited

Loading

MisRob commented Sep 11, 2024 •

edited

Loading