167 fix pagination and add event enhancements

[rabgonzalez]

No description provided.

[Copilot]

Pull Request Overview

This PR addresses pagination issues while enhancing event-related UI translations. Key changes include updating translation files with additional event messaging, simplifying post concatenation logic in several screens, and refining pagination conditions in activities loading.

Reviewed Changes

Copilot reviewed 11 out of 11 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
App/translations/{fr,es,en,de}.json	Added new keys for event progress and final messages in multiple locales.
App/src/utils/Utils.tsx	Updated convertQuantityToString to use optional chaining for the fallback.
App/src/screens/ProfileScreen.tsx	Simplified the logic for appending new posts by removing deduplication.
App/src/screens/HomeScreen.tsx	Refined concatenation of posts and adjusted createdAt slicing for pagination.
App/src/screens/EventsScreen.tsx	Added UI elements to display event progress and final message.
App/src/screens/ActivitiesScreen.tsx	Modified the pagination condition in loadMore function.
App/src/repositories/PostRepository.tsx	Updated API field names and enhanced error logging.

Comments suppressed due to low confidence (1)

App/src/screens/ActivitiesScreen.tsx:64

• The previous pagination condition checked if the loaded activity count was less than the expected total (pageNum.current * limit), which might have been used to prevent loading incomplete pages. Verify that changing the condition to activities.length === 0 appropriately handles the pagination logic.

if (isLoadingMore || activities.length === 0) return;

[Copilot]

Since the quantity parameter is statically typed as a number, the use of optional chaining may be unnecessary. Consider using quantity.toString() directly unless there is an explicit case where quantity can be undefined.

Suggested change

	return quantity?.toString();
	return quantity.toString();