Add ability to bulk select cards from the same bank in the Card filter #53389

SzymczakJ · 2024-12-02T16:25:13Z

Explanation of Change

This PR adds Card feeds secion to Card filter on Search page, which is only visible to workspace admin. With this PR admin will be able to bulk select cards from the same feed.
PR also makes workspace admins see all the cards linked to workspace(taken from cards_ Onyx key).
Card feeds secion is built from workspace feeds(cards_ Onyx key) and domain feeds which are separeted from cardList object(cardList Onyx key), because right now New Dot doesn't fully support domain cards and it's the only Onyx object that contains it. Admin cannot see all domain cards yet.

Fixed Issues

$ #53231
PROPOSAL: N/A

Tests

Test on account that has at least three workspaces with linked expensify cards and three workspaces with linked company cards(both of them with admin permissions) and a few domain cards linked(*I think we can only assign domain cards on staging by adhoc builds so this part only applies to staging testing).
Enter advanced filters on search page and go to card filter.
Try scrolling card filter page, selecting and deselecting individual cards.
Try selecting card feeds and make sure connected cards also get selected.
Try unselecting one of the card feed's individual cards and make sure card feed is also unselected.
Try using input to filter cards.
Make sure that after saving cards are visible on advanced filters page and after showing results also in the search page input.

Offline tests

QA Steps

Same as tests. Please make sure domain feeds are tested well as I didn't have access to any domain feed.

PR Author Checklist

Screenshots/Videos

Android: Native

android.mov

Android: mWeb Chrome

androidweb.mov

iOS: Native

ios.mov

iOS: mWeb Safari

ioweb.mov

MacOS: Chrome / Safari

web.mov

MacOS: Desktop

desktop.mov

Kicu

Most of these stuff looks ok, although logic is pretty complex 😅
Left some small comments

src/pages/Search/SearchAdvancedFiltersPage/SearchFiltersCardPage.tsx

Kicu

Dropped small comments

tests/unit/Search/buildSubstitutionsMapTest.ts

tests/unit/Search/buildCardFilterDataTest.ts

SzymczakJ · 2024-12-17T13:59:08Z

At the moment the API command that downloads card data is working only on staging so make sure you have it turned on.

luacmartins · 2024-12-18T15:01:09Z

Yea, let's get @rayane-djouah to review this since they have context

luacmartins · 2024-12-18T15:01:47Z

@rayane-djouah let's prioritize reviewing this one once you're online!

rayane-djouah · 2024-12-18T17:05:10Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified tests pass on all platforms & I tested again on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

src/components/Search/SearchPageHeader.tsx

src/pages/Search/SearchAdvancedFiltersPage/SearchFiltersCardPage.tsx

SzymczakJ · 2024-12-19T11:50:53Z

Fixed your comments @rayane-djouah

rayane-djouah · 2024-12-19T15:22:47Z

src/pages/Search/SearchAdvancedFiltersPage/SearchFiltersCardPage.tsx

+            bank,
+            correspondingCardIDs,
+            iconStyles,
+            cardFeedLabel: isBankRepeating ? domainName : undefined,


This will cause the card feed label to be displayed in expensify-policy${policyID}.exfy default format for workspaces without a custom domain.

We need to display a human-readable name for Expensify policy domain names similar to what we already do here:

App/src/pages/settings/Wallet/PaymentMethodList.tsx

Lines 217 to 225 in 653a06b

const getDescriptionForPolicyDomainCard = (domainName: string): string => {

// A domain name containing a policyID indicates that this is a workspace feed

const policyID = domainName.match(CONST.REGEX.EXPENSIFY_POLICY_DOMAIN_NAME)?.[1];

if (policyID) {

const policy = PolicyUtils.getPolicy(policyID.toUpperCase());

return policy?.name ?? domainName;

}

return domainName;

};

I've applied your suggestion but have no domain cards to test it. When you test this Pr again please look at this part.

rayane-djouah · 2024-12-19T19:38:30Z

src/pages/Search/SearchAdvancedFiltersPage/SearchFiltersCardPage.tsx

+    const text = card.bank === CONST.EXPENSIFY_CARD.BANK ? card.bank : cardName;
+
+    return {
+        lastFourPAN: card.lastFourPAN,


Physical cards that have not yet been issued lack a lastFourPAN and are uniformly labeled as Expensify Card:

I think we should consider either modifying how these cards are displayed or not showing the unissued cards (that do not have a lastFourPAN) at all.

App/src/pages/settings/Wallet/Card/BaseGetPhysicalCard.tsx

Line 106 in 2199bc8

const cardToBeIssued = domainCards.find((card) => !card?.nameValuePairs?.isVirtual && card?.state === CONST.EXPENSIFY_CARD.STATE.STATE_NOT_ISSUED);

@luacmartins, what are your thoughts on this?

I suppose you cannot pay with a unissued card, so there's no point in searching report with them. We could just filter them out. WDYT @luacmartins

I agree. Let's filter out unissued cards. Nice catch!

rayane-djouah · 2024-12-19T19:45:09Z

src/pages/Search/SearchAdvancedFiltersPage/SearchFiltersCardPage.tsx

+    // When user is admin of a workspace he sees all the cards of workspace under cards_ Onyx key
+    const allWorkspaceCards: CardFilterItem[] = Object.values(workspaceCardFeeds)
+        .filter((cardFeed) => !isEmptyObject(cardFeed))
+        .flatMap((cardFeed) => {
+            return Object.values(cardFeed as Record<string, Card>)
+                .filter((card) => card && CardUtils.isCard(card) && !userCardList?.[card.cardID])
+                .map((card) => createIndividualCardFilterItem(card, selectedCards, iconStyles));
+        });


The admin of a workspace currently cannot differentiate between cards assigned to them and those assigned to other members:

Before After

@Expensify/design, @luacmartins, should we consider modifying the card list item to address this issue?

Hmm yeah, this makes me wonder if we should reconsider the avatars we use for cards... should we consider something more like this?

Ooo I could definitely be into something like that.

Can you link the whole figma for that design? Also does that mean that we should grup cards in Card Filter by user? @shawnborton

My thinking is that this would work much like Workspace avatars do...

The workspace itself just uses a single avatar. In this case, the feed itself uses a single avatar and that's the big card logo.

But then individual users/cards within the feed get the stacked avatar + card treatment like I'm showing above.

Before we commit to that, let's see what @JmillsExpensify @trjExpensify @Expensify/design @joekaufmanexpensify thinks though. I think it could help solve this issue though.

I'm not really sure how the whole card filter should look like though. Would you give me the link to this Figma? Previously the desing didn't contain any groupings like your screenshot does. Or maybe this screenshot comes from another desing and I should only add these avatars to card filter? @shawnborton

I was thinking it would look something like this:

So the main card feed is an option at the very top. Then below we have individual cards. That's just like you are doing above. But the only difference is how we display the avatar and card name. Thoughts? cc @JmillsExpensify @joekaufmanexpensify @Expensify/design

Personally I'm super into that. We get ALL the info in there and it looks really nice.

Looks great to me! This change would apply to third party cards too, right?

Looks great to me as well! Thanks for clarification

rayane-djouah · 2024-12-19T20:20:16Z

src/pages/Search/SearchAdvancedFiltersPage/SearchFiltersCardPage.tsx

-            data: cards,
-            shouldShow: cards.length > 0,
+            title: translate('search.filters.card.individualCards'),
+            data: individualCardsSectionData.filter((item) => item.text?.toLocaleLowerCase().includes(debouncedSearchTerm.toLocaleLowerCase())),


Is it necessary to include fields other than item.text in the search, such as item.lastFourPAN?

It might be a good idea to allow for lastFourPAN search too

rayane-djouah · 2024-12-19T20:27:34Z

src/components/Search/SearchPageHeaderInput.tsx

Console error:

I don't see such error, also everything that could cause "update max depth exceeded" seems wrapped in useMemo, so I don't see a case when this error pops up. Do you have some specific steps of reproduction for this error?

rayane-djouah · 2024-12-19T20:32:06Z

src/pages/Search/SearchAdvancedFiltersPage/SearchFiltersCardPage.tsx

BUG: When a feed list item is selected, the list automatically scrolls down to the individual cards. Conversely, selecting an individual card causes the list to automatically scroll up to the corresponding feed list item:

Screen.Recording.2024-12-19.at.9.28.06.PM.mov

rayane-djouah · 2024-12-19T20:35:40Z

tests/unit/Search/buildCardFilterDataTest.ts

+        },
+    };
+});
+


@SzymczakJ I'm testing with the mock data below. Is the data correct, or am I missing something?

Code

Onyx.merge('cardList', { '21588678': { accountID: 1, bank: 'Expensify Card', cardID: 21588678, cardName: '455594XXXXXX1138', domainName: 'expensify-005AA2EAC6D4E280.exfy', lastFourPAN: '1138', }, '21588684': { accountID: 1, bank: 'Expensify Card', cardID: 21588684, cardName: '', domainName: 'expensify-FD17559D0E7ED371.exfy', lastFourPAN: '', }, '21589202': { accountID: 1, bank: 'Expensify Card', cardID: 21589202, cardName: '455594XXXXXX6232', domainName: 'expensify-FD17559D0E7ED371.exfy', lastFourPAN: '6232', }, '21604933': { accountID: 1, bank: 'vcf', cardID: 21604933, cardName: '480801XXXXXX1601', domainName: 'expensify-005AA2EAC6D4E280.exfy', lastFourPAN: '1601', }, '11111111': { accountID: 1, bank: 'Expensify Card', cardID: 11111111, cardName: '455594XXXXXX1139', domainName: 'testDomain.com', lastFourPAN: '1139', }, '234523452345': { cardID: 234523452345, state: 3, bank: 'Expensify Card', availableSpend: 10000, domainName: 'expensify.com', lastFourPAN: '2345', isVirtual: true, cardholderFirstName: 'Test', cardholderLastName: 'Test', }, '234523452346': { cardID: 234523452346, state: 4, bank: '1000', availableSpend: 10000, domainName: 'expensify.com', lastFourPAN: '2346', isVirtual: false, }, }); Onyx.merge(`cards_18680694_vcf`, { '21593492': { accountID: 17822766, bank: 'vcf', cardID: 21593492, cardName: '480801XXXXXX9411', domainName: 'expensify-7BFA00039DEB0D94.exfy', lastFourPAN: '9411', }, '21604933': { accountID: 17822766, bank: 'vcf', cardID: 21604933, cardName: '480801XXXXXX1601', domainName: 'expensify-FD17559D0E7ED371.exfy', lastFourPAN: '1601', }, '21638320': { accountID: 17822777, bank: 'vcf', cardID: 21638320, cardName: '480801XXXXXX2617', domainName: 'expensify-7BFA00039DEB0D94.exfy', lastFourPAN: '2617', }, '21638598': { accountID: 14826403, bank: 'vcf', cardID: 21638598, cardName: '480801XXXXXX2111', domainName: 'expensify-FD17559D0E7ED371.exfy', lastFourPAN: '2111', }, cardList: { test: '231:1111111', }, }); Onyx.merge('cards_18465979_Expensify Card', { '21588678': { accountID: 17861101, bank: 'Expensify Card', cardID: 21588678, cardName: '455594XXXXXX1134', domainName: 'expensify-005AA2EAC6D4E280.exfy', lastFourPAN: '1134', }, '21588684': { accountID: 18118340, bank: 'Expensify Card', cardID: 21588684, cardName: '', domainName: 'expensify-005AA2EAC6D4E280.exfy', lastFourPAN: '', }, }); Onyx.merge('cards_18643109_Expensify Card', { '21589168': { accountID: 17822777, bank: 'Expensify Card', cardID: 21589168, cardName: '455594XXXXXX4163', domainName: 'expensify-7BFA00039DEB0D94.exfy', lastFourPAN: '4163', }, '21589182': { accountID: 17822780, bank: 'Expensify Card', cardID: 21589182, cardName: '', domainName: 'expensify-7BFA00039DEB0D94.exfy', lastFourPAN: '', }, '21589202': { accountID: 17822780, bank: 'Expensify Card', cardID: 21589202, cardName: '455594XXXXXX6232', domainName: 'expensify-7BFA00039DEB0D94.exfy', lastFourPAN: '6232', }, '21638322': { accountID: 14826403, bank: 'Expensify Card', cardID: 21638322, cardName: '', domainName: 'expensify-7BFA00039DEB0D94.exfy', lastFourPAN: '', }, });

I limited the mocks to have only what we need, Card objects are enormous and if I wanted to include all the data, that BE gives us, then These mocks would take 2.5x more code lines.

src/libs/actions/Search.ts

luacmartins

Nice work so far! We have a few pending items to address from the last review but looking good otherwise

rayane-djouah · 2025-01-01T11:16:35Z

There are merge conflicts that need to be resolved

SzymczakJ added 2 commits December 2, 2024 16:16

add expensify card feeds to card filter

951f85b

add company card feeds to card filter

4113519

luacmartins self-requested a review December 2, 2024 17:46

SzymczakJ added 10 commits December 3, 2024 10:12

Merge branch 'main' into @szymczak/add-feeds-to-card-filter

e0d5bf8

add handling of domain feeds

9336e8f

add search input

defc543

improve naming

98b3512

fix typescript

a5545b7

fix typescript

6ebe579

add lowercase filtring

a1ae60e

wrap workspaceFeeds data in useMemo

d9f0e8a

fix filter not appearing bug

42ecedc

fix export bug

93e23ca

SzymczakJ changed the title ~~WIP Add ability to bulk select cards from the same bank in the Card filter~~ Add ability to bulk select cards from the same bank in the Card filter Dec 6, 2024

fix linter

00f3ad8

Kicu reviewed Dec 6, 2024

View reviewed changes

SzymczakJ added 8 commits December 9, 2024 11:42

fix PR comments

cfb2417

fix wrong card names bug

6f8efac

Merge branch 'main' into @szymczak/add-feeds-to-card-filter

bd92551

add tests to card filter data generation

5d93a9d

fix buildSubstitutionsMapTest tests

ab009cc

Merge branch 'main' into @szymczak/add-feeds-to-card-filter

e9cb9da

clean up Search tests

cec56f7

delete redundant comments

9068aa8

Kicu reviewed Dec 11, 2024

View reviewed changes

tests/unit/Search/buildSubstitutionsMapTest.ts Outdated Show resolved Hide resolved

tests/unit/Search/buildCardFilterDataTest.ts Show resolved Hide resolved

tests/unit/Search/buildCardFilterDataTest.ts Outdated Show resolved Hide resolved

SzymczakJ added 5 commits December 11, 2024 17:56

fix PR comments

313bb46

Merge branch 'main' into @szymczak/add-feeds-to-card-filter

0f274f9

fix typo

a48f976

fix linter warnings

5f21294

add api call

b4e5aab

SzymczakJ mentioned this pull request Dec 18, 2024

[$500] [MacOS Chrome / iOS Chrome] Chrome Browser Has Mistaken Form Fields For Inputs in Expensify Chat #47939

Open

6 tasks

luacmartins requested review from rayane-djouah and removed request for jayeshmangwani December 18, 2024 15:01

Merge branch 'main' into @szymczak/add-feeds-to-card-filter

947d918

rayane-djouah suggested changes Dec 18, 2024

View reviewed changes

src/pages/Search/SearchAdvancedFiltersPage/SearchFiltersCardPage.tsx Outdated Show resolved Hide resolved

rayane-djouah suggested changes Dec 19, 2024

View reviewed changes

src/pages/Search/SearchAdvancedFiltersPage/SearchFiltersCardPage.tsx Outdated Show resolved Hide resolved

fix PR comments

6ad3f86

luacmartins requested a review from rayane-djouah December 19, 2024 14:23

rayane-djouah suggested changes Dec 19, 2024

View reviewed changes

rayane-djouah reviewed Dec 19, 2024

View reviewed changes

src/libs/actions/Search.ts Outdated Show resolved Hide resolved

fix PR comments

d340930

luacmartins requested a review from rayane-djouah December 30, 2024 19:35

luacmartins reviewed Dec 30, 2024

View reviewed changes

SzymczakJ added 4 commits January 7, 2025 09:49

Merge branch 'main' into @szymczak/add-feeds-to-card-filter

719a972

fix card filter SelectionList selection behaviour

306f6c6

filter out unissued cards in card filter page

415ef30

include lastFourPan in card filter search

00dc930

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add ability to bulk select cards from the same bank in the Card filter #53389

Add ability to bulk select cards from the same bank in the Card filter #53389

SzymczakJ commented Dec 2, 2024 •

edited

Loading

Kicu left a comment

Kicu left a comment

SzymczakJ commented Dec 17, 2024

luacmartins commented Dec 18, 2024

luacmartins commented Dec 18, 2024

rayane-djouah commented Dec 18, 2024 •

edited

Loading

SzymczakJ commented Dec 19, 2024

rayane-djouah Dec 19, 2024

SzymczakJ Jan 7, 2025

rayane-djouah Dec 19, 2024

SzymczakJ Dec 20, 2024

luacmartins Dec 30, 2024

rayane-djouah Dec 19, 2024

shawnborton Dec 19, 2024

dannymcclain Dec 19, 2024

SzymczakJ Dec 20, 2024 •

edited

Loading

shawnborton Dec 20, 2024

SzymczakJ Jan 7, 2025 •

edited

Loading

shawnborton Jan 7, 2025

dannymcclain Jan 7, 2025

joekaufmanexpensify Jan 7, 2025

SzymczakJ Jan 8, 2025

rayane-djouah Dec 19, 2024

luacmartins Dec 30, 2024

rayane-djouah Dec 19, 2024

SzymczakJ Dec 20, 2024

rayane-djouah Dec 19, 2024

rayane-djouah Dec 19, 2024

SzymczakJ Dec 20, 2024

luacmartins left a comment

rayane-djouah commented Jan 1, 2025

	const getDescriptionForPolicyDomainCard = (domainName: string): string => {
	// A domain name containing a policyID indicates that this is a workspace feed
	const policyID = domainName.match(CONST.REGEX.EXPENSIFY_POLICY_DOMAIN_NAME)?.[1];
	if (policyID) {
	const policy = PolicyUtils.getPolicy(policyID.toUpperCase());
	return policy?.name ?? domainName;
	}
	return domainName;
	};

Add ability to bulk select cards from the same bank in the Card filter #53389

Are you sure you want to change the base?

Add ability to bulk select cards from the same bank in the Card filter #53389

Conversation

SzymczakJ commented Dec 2, 2024 • edited Loading

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Kicu left a comment

Choose a reason for hiding this comment

Kicu left a comment

Choose a reason for hiding this comment

SzymczakJ commented Dec 17, 2024

luacmartins commented Dec 18, 2024

luacmartins commented Dec 18, 2024

rayane-djouah commented Dec 18, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

SzymczakJ commented Dec 19, 2024

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

SzymczakJ Dec 20, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

SzymczakJ Jan 7, 2025 • 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

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

luacmartins left a comment

Choose a reason for hiding this comment

rayane-djouah commented Jan 1, 2025

SzymczakJ commented Dec 2, 2024 •

edited

Loading

rayane-djouah commented Dec 18, 2024 •

edited

Loading

SzymczakJ Dec 20, 2024 •

edited

Loading

SzymczakJ Jan 7, 2025 •

edited

Loading