768 Add ViewMessages Intent & SearchCriteria Context by symphony-jean-michael · Pull Request #797 · finos/FDC3

symphony-jean-michael · 2022-08-08T15:41:31Z

This PR adds the 'ViewMessages' intent.
See initial discussion #768

netlify · 2022-08-08T15:41:42Z

✅ Deploy Preview for lambent-kulfi-cf51a7 canceled.

Name	Link
🔨 Latest commit	`41b3384`
🔍 Latest deploy log	https://app.netlify.com/sites/lambent-kulfi-cf51a7/deploys/636cdb132d5c9200094fd968

mistryvinay · 2022-08-24T10:15:52Z

+| Property         | Type            | Required | Example Value        |
+|------------------|-----------------|----------|----------------------|
+| `type`           | string          | Yes      | `'fdc3.searchCriteria'`     |
+| `contexts`    | (Instrument&#124;<br>Contact&#124;<br>Organization&#124;<br>string)[]  | Yes      | <pre>[<br>&emsp;&emsp;{<br>&emsp;&emsp;&emsp;&emsp;"type": "fdc3.instrument",<br>&emsp;&emsp;&emsp;&emsp;"id": {<br>&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;"ticker": "AAPL"<br>&emsp;&emsp;&emsp;&emsp;}<br>&emsp;&emsp;},<br>&emsp;&emsp;{<br>&emsp;&emsp;&emsp;&emsp;"type": "fdc3.contact",<br>&emsp;&emsp;&emsp;&emsp;"name":"Jane Doe",<br>&emsp;&emsp;&emsp;&emsp;"id": {<br>&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;"email": "jane.doe@mail.com"<br>&emsp;&emsp;&emsp;&emsp;}<br>&emsp;&emsp;},<br>&emsp;&emsp;{<br>&emsp;&emsp;&emsp;&emsp;"type": "fdc3.organization",<br>&emsp;&emsp;&emsp;&emsp;"name":"Symphony",<br>&emsp;&emsp;},<br>&emsp;&emsp;"#OrderID45788422",<br>]</pre> |


Does this example need to be revisited? removing the html entities.

Hi @mistryvinay
I removed the HTML entities from the example.

Actually, the HTML entities are there to make it render on the web. Markdown has some shortcomings when it comes to code examples...

Heres what it looks like in github's preview without the HTML entities:

and with them:

Use the rich preview (the file icon) to see the markdown rendered:

We need to have another go at asking FINOS to adjust the netlify config to ensure it builds previews for PRs like this - right now it only builds if it detects changes in the /website directory...

OK. @kriswest Do you want me to restore the changes (HTML entities)?

Managed to track down the preview - still showing state before they were removed:

If you merge master into your PR (needs doing anyway) it should refresh so you can see it without at: https://deploy-preview-797--lambent-kulfi-cf51a7.netlify.app/docs/next/context/ref/searchcriteria (once the deploy has run).

From memory docusaurus really struggles with long code lines in tables. Might be worth a check first in case I'm mis-remembering.

mistryvinay

Think the detail/example may need reworking to remove the html entitites. (docs/context/ref/SearchCriteria.md)

kriswest

I'd like to discuss this further as I think there are a few ways it could be further clarified/future proofed. See individual comments

kriswest · 2022-09-01T09:17:32Z

+---
+# `SearchCriteria`
+
+A context type representing a search criteria that can be used to filter and display messages from a chat.


Given the generic name, type name and structure (an array of context objects), the description should also be generic (but can use chat as an example).

Suggested change

A context type representing a search criteria that can be used to filter and display messages from a chat.

A context type that represents a simple search criterion, based on a list of other context objects, that can be used to search or filter content in an application (such as messages in a chat app).

I'm tempted to also suggest tweaking the name to acknowledge the simplicity of the criterion (a bag of contexts) in case we want to introduce more complex search types in future (but haven't come to a conclusion on that yet - after all we might expand this one with additional fields instead...).

I also think an explanation of how multiple contexts in the list should be interpreted (to encourage similar behaviour). Should they be combined with AND or OR?

If variation in behaviour is expected or desirable an enumerated field should be added for that (e.g. combinationLogic: "AND") or the contexts field replaced with separate fields (e.g. contexts: { and: [...], or: [...], not: [...]}).

@kriswest I like your idea about using contexts: { and: [...], or: [...], not: [...]}
It's very generic :)
I'll update the PR accordingly.

kriswest · 2022-09-01T09:18:06Z

+| Property         | Type            | Required | Example Value        |
+|------------------|-----------------|----------|----------------------|
+| `type`           | string          | Yes      | `'fdc3.searchCriteria'`     |
+| `contexts`    | (Instrument&#124;<br>Contact&#124;<br>Organization&#124;<br>string)[]  | Yes      | `[{ type: "fdc3.instrument", id: { ticker: "AAPL" }}, { type: "fdc3.contact", name: "Jane Doe", id: { email: "jane.doe@mail.com" }}, { type: "fdc3.organization", name: "Symphony" }, "#OrderID45788422"]` |


I'd recommend restoring the HTML entities as they make a big difference when rendered (despite looking nuts in the markdown source)

I'm struggling with the field name as it doesn't accept arbitrary contexts, rather several specific types - one of which isn't actually a context but a string.

Either it needs renaming to criteria or add optional named fields for each type (which allows setting none to reset the filter BTW).

Do you expect more than one contact or instrument to be added? If so those separate fields would also be arrays, otherwise single, optional objects.

Do you think this might extend to additional types in future. That is more likely if the type is generic and used beyond chat. In which case contexts is a valid name, if the string criteria is moved to a separate field.

I'll rename 'contexts' into 'criteria'.

@kriswest I don't get your point: 'If so those separate fields would also be arrays'

I have in mind to use something like that in case of multiple Contact, Instrument:

criteria: [ { type: "fdc3.contact", name: "Jane Doe", id: { email: "jane.doe@mail.com" } }, { type: "fdc3.contact", name: "Jean Dupont", id: { email: "jean.dupond@mail.com" } }, { type: "fdc3.organization", name: "Symphony" }, { type: "fdc3.instrument", id: { ticker: "AAPL" } }, { type: "fdc3.instrument", id: { ticker: "ABC" } } ]

So, there is only 1 array accepting any Contact, Intents, et ....
Of course, what is missing here is the AND/OR/NOT criteria ;)

Do you expect more than one contact or instrument to be added? If so those separate fields would also be arrays, otherwise single, optional objects.

What I meant was, if you separated out the 'contexts' into separate fields for each type, would you be accept just a single contact or an array of contacts.

I have in mind to use only one array (criteria) and not one field/array per type.
This array could contain objects of different types (like Contact and Organization and Instrument...)
@kriswest Do you agree with this solution? Or would you prefer an array by type?

kriswest · 2022-09-01T09:22:01Z

+---
+# `ViewMessages`
+
+Search and display a list of messages to the user.


Suggested change

Search and display a list of messages to the user.

Search and display a list of messages (for example in a chat application or CRM) to the user.

Thanks. I updated the PR.

kriswest · 2022-09-01T09:22:32Z

+
+## Example
+
+Request to display messages for a specific ticker:


Suggested change

Request to display messages for a specific ticker:

Request display of messages relating to a specific `fdc3.instrument` (representing a ticker):

Thanks. I updated the PR.

kriswest · 2022-09-01T09:24:13Z

+fdc3.raiseIntent('ViewMessages', searchCriteria);
+```
+
+Request to display messages for a specific **contact**:


Suggested change

Request to display messages for a specific **contact**:

Request display of messages relating to a specific `fdc3.contact`:

Thanks. I updated the PR.

kriswest · 2022-09-01T09:26:29Z

+fdc3.raiseIntent('ViewMessages', searchCriteria);
+```
+
+Request to display messages for a specific **organization**:


Probably redundant. It'd be more succinct to add a line of copy either at the start of the example section or under possible contexts explaining that any appropriate contexts (or combination of contexts!) can be added to the search criteria.

kriswest · 2022-09-01T09:31:55Z

+fdc3.raiseIntent('ViewMessages', searchCriteria);
+```
+
+Request to display messages with **multiples** criteria:


Suggested change

Request to display messages with **multiples** criteria:

Request display of messages matching _multiple_ criteria:

Again, we need an indication of how the multiple criteria are expected to be combined.

kriswest · 2022-09-01T09:32:48Z

+* [Instrument](../../context/ref/Instrument)
+* [Contact](../../context/ref/Contact)
+* [Organization](../../context/ref/Organization)
+* [SearchCriteria](../../context/ref/SearchCriteria)


Suggested change

* [Instrument](../../context/ref/Instrument)

* [Contact](../../context/ref/Contact)

* [Organization](../../context/ref/Organization)

* [SearchCriteria](../../context/ref/SearchCriteria)

* [SearchCriteria](../../context/ref/SearchCriteria)

* [Instrument](../../context/ref/Instrument)

* [Contact](../../context/ref/Contact)

* [Organization](../../context/ref/Organization)

Might as well promote SearchCriteria to the head of the list as its of most interest here

Ok I updated the order.

kriswest · 2022-09-01T09:33:08Z

  Email = 'fdc3.email',
  Instrument = 'fdc3.instrument',
  InstrumentList = 'fdc3.instrumentList',
+  Nothing = 'fdc3.nothing',


ha, good catch

symphony-jean-michael · 2022-09-02T08:14:54Z

Hi @kriswest
I updated the PR to take into account your remarks.
For the criteria operators, I did what we discussed yesterday, and I updated the description of SearchCriteria to explain that the operators are not defined in the SearchCriteira, but it is up to the application that receives the Intent to choose and apply the operators. (See https://github.com/finos/FDC3/pull/797/files#diff-10b12f0cd7551554329f046508ee812f15561a1ceb30fdd0b99e5e02005a01f6R26 )
Could you have a second look at the PR please?
Thanks :)

kriswest · 2022-09-05T13:02:59Z

Could you have a second look at the PR please?

I haven't yet had a chance for a full review, but as the query fields are restricted so is the use-case. Hence, I still think the type should be scoped for chat. I.e. fdc3.chat.searchCriteria

symphony-jean-michael · 2022-09-06T07:46:40Z

@kriswest You're right, I renamed fdc3.searchCriteria into fdc3.chat.searchCriteria

mistryvinay · 2022-10-04T11:47:28Z

Including notes from our last meeting (Sep 2022). With recommended changes for this PR.

768 Add ViewMessages Intent & SearchCriteria Context #797
- Is this a general search criteria, or a specific search criteria for chat? The context specifically limits the criteria and query construction that can be used in a search...
  - Option 1: Make this more flexible to support all search purposes
    - We don't want to define a query for all use-cases at the moment, it would be too large an undertaking
  - Option 2: Refactor it to be chat specific, with a rename to fdc3.chat.searchcriteria
- Further options for supporting more complex search criteria were discussed
  - E.g. use a Google type search
    - All search clauses are combined with OR
    - Then ranked results are returned based on those OR search criteria values
    - Ranked in order of filter word occurrences
  - Empty search criteria could supported to allow reset of filters (which is a common issue in FDC3 for filters based on context broadcasts)
  - Rename contexts array to criteria to acknowledge that it may contain strings, not just contexts

symphony-jean-michael · 2022-10-04T12:38:57Z

@mistryvinay FYI:

"Is this a general search criteria, or a specific search criteria for chat?"
The Option 2: has been chosen. It has been renamed to fdc3.chat.searchcriteria Done ✅
"Further options for supporting more complex search criteria were discussed"
- "E.g. use a Google type search"
  There is a paragraph in SearchCriteria.md explaining there are no implementation details in the FDC3 standard. It is up to the application that receives the intent to define how it handles the criteria. Done ✅
- "Empty search criteria could supported to allow reset of filters (which is a common issue in FDC3 for filters based on context broadcasts)"
  I've just added a new line about it in the SearchCriteria.md file. Done ✅
- "Rename contexts array to criteria to acknowledge that it may contain strings, not just contexts" Done ✅

kriswest

Needs a changelog entry and I think SearchCriteria should be renamed ChatSearchCriteria. Otherwise LGTM

kriswest · 2022-11-03T12:39:44Z

+---
+# `SearchCriteria`
+
+A context type that represents a simple search criterion, based on a list of other context objects, that can be used to search or filter content in an application (such as messages in a chat app).


Suggested change

A context type that represents a simple search criterion, based on a list of other context objects, that can be used to search or filter content in an application (such as messages in a chat app).

A context type that represents a simple search criterion, based on a list of other context objects, that can be used to search or filter messages in a chat application.

Change description as we're only covering that use case now

kriswest · 2022-11-03T12:40:37Z

@@ -0,0 +1,64 @@
+---
+id: SearchCriteria


We should probably rename this ChatMessageSearchCriteria or ChatSearchCriteria as this doesn't cover all types of search and something in the future might.

kriswest · 2022-11-03T12:41:30Z

+| Property         | Type            | Required | Example Value        |
+|------------------|-----------------|----------|----------------------|
+| `type`           | string          | Yes      | `'fdc3.chat.searchCriteria'`     |
+| `criteria` | (Instrument&#124;<br>Contact&#124;<br>Organization&#124;<br>string)[] | Yes | <pre>[<br>&emsp;&emsp;{<br>&emsp;&emsp;&emsp;&emsp;"type": "fdc3.instrument",<br>&emsp;&emsp;&emsp;&emsp;"id": {<br>&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;"ticker": "AAPL"<br>&emsp;&emsp;&emsp;&emsp;}<br>&emsp;&emsp;},<br>&emsp;&emsp;{<br>&emsp;&emsp;&emsp;&emsp;"type": "fdc3.contact",<br>&emsp;&emsp;&emsp;&emsp;"name":"Jane Doe",<br>&emsp;&emsp;&emsp;&emsp;"id": {<br>&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;"email": "jane.doe@mail.com"<br>&emsp;&emsp;&emsp;&emsp;}<br>&emsp;&emsp;},<br>&emsp;&emsp;{<br>&emsp;&emsp;&emsp;&emsp;"type": "fdc3.organization",<br>&emsp;&emsp;&emsp;&emsp;"name":"Symphony",<br>&emsp;&emsp;},<br>&emsp;&emsp;"#OrderID45788422",<br>]</pre> |


Suggested change

| `criteria` | (Instrument| Contact| Organization| string)[] | Yes | <pre>[ &emsp;&emsp;{ &emsp;&emsp;&emsp;&emsp;"type": "fdc3.instrument", &emsp;&emsp;&emsp;&emsp;"id": { &emsp;&emsp;&emsp;&emsp;&emsp;&emsp;"ticker": "AAPL" &emsp;&emsp;&emsp;&emsp;} &emsp;&emsp;}, &emsp;&emsp;{ &emsp;&emsp;&emsp;&emsp;"type": "fdc3.contact", &emsp;&emsp;&emsp;&emsp;"name":"Jane Doe", &emsp;&emsp;&emsp;&emsp;"id": { &emsp;&emsp;&emsp;&emsp;&emsp;&emsp;"email": "jane.doe@mail.com" &emsp;&emsp;&emsp;&emsp;} &emsp;&emsp;}, &emsp;&emsp;{ &emsp;&emsp;&emsp;&emsp;"type": "fdc3.organization", &emsp;&emsp;&emsp;&emsp;"name":"Symphony", &emsp;&emsp;}, &emsp;&emsp;"#OrderID45788422", ]</pre> |

| `criteria` | (Instrument | Contact | Organization | string)[] | Yes | <pre>[ &emsp;&emsp;{ &emsp;&emsp;&emsp;&emsp;"type": "fdc3.instrument", &emsp;&emsp;&emsp;&emsp;"id": { &emsp;&emsp;&emsp;&emsp;&emsp;&emsp;"ticker": "AAPL" &emsp;&emsp;&emsp;&emsp;} &emsp;&emsp;}, &emsp;&emsp;{ &emsp;&emsp;&emsp;&emsp;"type": "fdc3.contact", &emsp;&emsp;&emsp;&emsp;"name":"Jane Doe", &emsp;&emsp;&emsp;&emsp;"id": { &emsp;&emsp;&emsp;&emsp;&emsp;&emsp;"email": "jane.doe@mail.com" &emsp;&emsp;&emsp;&emsp;} &emsp;&emsp;}, &emsp;&emsp;{ &emsp;&emsp;&emsp;&emsp;"type": "fdc3.organization", &emsp;&emsp;&emsp;&emsp;"name":"Symphony", &emsp;&emsp;}, &emsp;&emsp;"#OrderID45788422", ]</pre> |

kriswest · 2022-11-03T12:42:11Z


 * [`fdc3.chart`](ref/Chart) ([schema](/schemas/next/chart.schema.json))
 * [`fdc3.chat.initSettings`](ref/ChatInitSettings) ([schema](/schemas/next/chatInitSettings.schema.json))
+* [`fdc3.chat.searchCriteria`](ref/SearchCriteria) ([schema](/schemas/next/searchCriteria.schema.json))


If renamed correct links

kriswest · 2022-11-03T12:42:51Z

  Portfolio = 'fdc3.portfolio',
  Position = 'fdc3.position',
-  Nothing = 'fdc3.nothing',
+  SearchCriteria = 'fdc3.chat.searchCriteria',


Correct this if renamed

kriswest · 2022-11-03T12:43:00Z

  name?: string;
 }

+export interface SearchCriteria {


Correct this if renamed

kriswest · 2022-11-03T12:43:11Z

  "Organization": ["https://fdc3.finos.org/schemas/next/organization.schema.json"],
  "Portfolio": ["https://fdc3.finos.org/schemas/next/portfolio.schema.json"],
  "Position": ["https://fdc3.finos.org/schemas/next/position.schema.json"],
+  "SearchCriteria": ["https://fdc3.finos.org/schemas/next/searchCriteria.schema.json"],


correct this if renamed

kriswest · 2022-11-03T12:43:38Z

+      }
+    }
+  },
+  "required": ["type", "criteria"]


Suggested change

"required": ["type", "criteria"]

"required": ["criteria"]

type is already required by context schema

kriswest · 2022-11-03T12:43:54Z

          "context/ref/Organization",
          "context/ref/Portfolio",
          "context/ref/Position",
+          "context/ref/SearchCriteria",


Correct this if renamed

kriswest · 2022-11-03T12:44:13Z

+      }
+    }
+  },
+  "required": ["type", "criteria"]


Suggested change

"required": ["type", "criteria"]

"required": ["criteria"]

Already required by context schema

symphony-jean-michael · 2022-11-10T13:31:45Z

Hi @kriswest
I've updated the PR accordingly to your remarks. Can you have a second look, please?
Thanks

symphony-jean-michael · 2022-12-08T13:19:23Z

FYI, this PR is included in new one #882

Add SearchCriteria Context

100f416

mistryvinay added enhancement New feature or request intents Context Data & Intents Contexts & Intents Discussion Group labels Aug 17, 2022

mistryvinay added this to the 2.1-candidates milestone Aug 24, 2022

mistryvinay requested a review from a team August 24, 2022 10:09

mistryvinay linked an issue Aug 24, 2022 that may be closed by this pull request

'View Messages' intent #768

Closed

mistryvinay requested review from kriswest and mistryvinay August 24, 2022 10:09

mistryvinay reviewed Aug 24, 2022

View reviewed changes

mistryvinay changed the title ~~Add ViewMessages Intent~~ 768 Add ViewMessages Intent Aug 24, 2022

symphony-jean-michael added 3 commits August 29, 2022 16:05

Lint file

2eb75d8

Remove the html entitites

a57e625

Add SeachCriteria link

6e1c104

mistryvinay mentioned this pull request Aug 30, 2022

Context Data & Intents Discussion group - 1 Sep 2022 #809

Closed

15 tasks

kriswest changed the title ~~768 Add ViewMessages Intent~~ 768 Add ViewMessages Intent & SearchCriteria Context Sep 1, 2022

kriswest requested changes Sep 1, 2022

View reviewed changes

symphony-jean-michael added 6 commits September 1, 2022 13:42

Merge remote-tracking branch 'upstream/master' into feature/ViewMessages

f236082

Update the description to be more generic

864f756

Reorder links

5f9b52c

Update descriptions

b517682

Restore the HTML entities

6ab7ece

Rename contexts in criteria

a54ae60

kriswest self-requested a review September 5, 2022 13:03

Rename fdc3.searchCriteria into fdc3.chat.searchCriteria

2b9931a

mistryvinay mentioned this pull request Oct 4, 2022

Context Data & Intents Discussion group - 6 Oct 2022 #826

Closed

14 tasks

symphony-jean-michael force-pushed the feature/ViewMessages branch from 37b5f77 to 2b9931a Compare October 4, 2022 12:31

Empty criteria

e1bb738

mistryvinay mentioned this pull request Oct 31, 2022

Context Data & Intents Discussion group - 3 Nov 2022 #845

Closed

12 tasks

kriswest requested changes Nov 3, 2022

View reviewed changes

symphony-jean-michael added 3 commits November 10, 2022 11:50

Rename SearchCriteria in ChatSearchCriteria

0172785

Rename searchCriteria in chatSearchCriteria

89d2fec

Add ViewMessages entry in the unreleased section of the changelog.md

41b3384

mistryvinay mentioned this pull request Nov 30, 2022

Context Data & Intents Discussion group - 1 Dec 2022 #868

Closed

9 tasks

symphony-jean-michael mentioned this pull request Dec 8, 2022

Symphony PRs in FDC3 2.1 candidates #882

Merged

symphony-jean-michael closed this Dec 12, 2022

kriswest modified the milestones: 2.1-candidates, 2.1 Apr 27, 2023

kriswest removed this from the 2.1 milestone Jul 25, 2023

bingenito mentioned this pull request Nov 6, 2023

Update to FDC3 2.1 finos/fdc3-dotnet#74

Closed

18 tasks

	A context type representing a search criteria that can be used to filter and display messages from a chat.
	A context type that represents a simple search criterion, based on a list of other context objects, that can be used to search or filter content in an application (such as messages in a chat app).

	Search and display a list of messages to the user.
	Search and display a list of messages (for example in a chat application or CRM) to the user.


		## Example

		Request to display messages for a specific ticker:

	Request to display messages for a specific ticker:
	Request display of messages relating to a specific `fdc3.instrument` (representing a ticker):

	Request to display messages with multiples criteria:
	Request display of messages matching _multiple_ criteria:

Conversation

symphony-jean-michael commented Aug 8, 2022

Uh oh!

netlify Bot commented Aug 8, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for lambent-kulfi-cf51a7 canceled.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mistryvinay left a comment

Choose a reason for hiding this comment

Uh oh!

kriswest left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

symphony-jean-michael Sep 1, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

kriswest Sep 5, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

symphony-jean-michael commented Sep 2, 2022

Uh oh!

kriswest commented Sep 5, 2022

Uh oh!

symphony-jean-michael commented Sep 6, 2022

Uh oh!

mistryvinay commented Oct 4, 2022

Uh oh!

symphony-jean-michael commented Oct 4, 2022

Uh oh!

kriswest left a comment

netlify Bot commented Aug 8, 2022 •

edited

Loading

symphony-jean-michael Sep 1, 2022 •

edited

Loading

kriswest Sep 5, 2022 •

edited

Loading