Skip to content

Conversation

@provokateurin
Copy link
Member

☑️ Resolves

Replaces #11991.
Only strings are allowed as values.

🛠️ API Checklist

🏁 Checklist

  • ⛑️ Tests (unit and/or integration) are included or not possible
  • 📘 API documentation in docs/ has been updated or is not required
  • 🔖 Capability is added or not needed

@provokateurin
Copy link
Member Author

/backport to stable29

@provokateurin
Copy link
Member Author

/backport to stable28

@provokateurin provokateurin force-pushed the fix/rich-object-non-string-values branch from a64826e to 338e811 Compare April 6, 2024 22:00
Copy link
Contributor

@SystemKeeper SystemKeeper left a comment

Choose a reason for hiding this comment

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

Works fine on iOS

Copy link
Member

@nickvergessen nickvergessen left a comment

Choose a reason for hiding this comment

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

PS: requires review from all requested persons
So blocking until everyone else approved

Copy link
Contributor

@Antreesy Antreesy left a comment

Choose a reason for hiding this comment

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

Adjusted frontend component to match new params. Nothing else is blocking

PS: backport to 27 might end up with conflicts, will handle it

@nickvergessen nickvergessen added feature: chat 💬 Chat and system messages feature: api 🛠️ OCS API for conversations, chats and participants labels Apr 8, 2024
@nickvergessen nickvergessen self-requested a review April 10, 2024 12:20
@nextcloud nextcloud deleted a comment from provokateurin Apr 10, 2024
@nickvergessen nickvergessen merged commit aca8fa1 into main Apr 10, 2024
@nickvergessen nickvergessen deleted the fix/rich-object-non-string-values branch April 10, 2024 12:27
@mahibi
Copy link

mahibi commented Apr 10, 2024

all fine for android talk as well, @nickvergessen

Antreesy added a commit that referenced this pull request Apr 18, 2024
- in #12021 type of server response was changed to strings, forget to cover tests
- Element.scrollTo is not implemented in JSDOM, need to mock it to avoid errors in Jest

Signed-off-by: Maksim Sukharev <[email protected]>
backportbot bot pushed a commit that referenced this pull request Apr 18, 2024
- in #12021 type of server response was changed to strings, forget to cover tests
- Element.scrollTo is not implemented in JSDOM, need to mock it to avoid errors in Jest

Signed-off-by: Maksim Sukharev <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review bug feature: api 🛠️ OCS API for conversations, chats and participants feature: chat 💬 Chat and system messages

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants