[feat] Notification Preferences Page #290

Dhanus3133 · 2024-07-15T16:55:26Z

Should fix #110, #148 and #255 issues

The Preference Page be like

nemesifier

Notes from our last discussion in the weekly meeting:

diff --git a/openwisp_notifications/api/urls.py b/openwisp_notifications/api/urls.py
index 597d2a7..82c236f 100644
--- a/openwisp_notifications/api/urls.py
+++ b/openwisp_notifications/api/urls.py
@@ -9,32 +9,47 @@ def get_api_urls(api_views=None):
     if not api_views:
         api_views = views
     return [
-        path('', views.notifications_list, name='notifications_list'),
-        path('read/', views.notifications_read_all, name='notifications_read_all'),
-        path('<uuid:pk>/', views.notification_detail, name='notification_detail'),
+        path('notification/', views.notifications_list, name='notifications_list'),
+        path('notification/read/', views.notifications_read_all, name='notifications_read_all'),
+        path('notification/<uuid:pk>/', views.notification_detail, name='notification_detail'),
         path(
-            '<uuid:pk>/redirect/',
+            'notification/<uuid:pk>/redirect/',
             views.notification_read_redirect,
             name='notification_read_redirect',
         ),
+        # path(
+        #     'notification/user-setting/',
+        #     views.notification_setting_list,
+        #     name='notification_setting_list',
+        # ),
+        # path(
+        #     'notification/user-setting/<uuid:pk>/',
+        #     views.notification_setting,
+        #     name='notification_setting',
+        # ),
         path(
-            'user-setting/',
-            views.notification_setting_list,
-            name='notification_setting_list',
-        ),
-        path(
-            'user-setting/<uuid:pk>/',
-            views.notification_setting,
-            name='notification_setting',
-        ),
-        path(
-            'ignore/',
+            'notification/ignore/',
             views.ignore_object_notification_list,
             name='ignore_object_notification_list',
         ),
         path(
-            'ignore/<str:app_label>/<str:model_name>/<uuid:object_id>/',
+            'notification/ignore/<str:app_label>/<str:model_name>/<uuid:object_id>/',
             views.ignore_object_notification,
             name='ignore_object_notification',
         ),
+        path(
+            'user/<uuid:user_id>/setting/',
+            # views.admin_user_organization_notification_setting,
+            # name='admin_user_organization_notification_setting',
+        ),
+        path(
+            'user/<uuid:user_id>/setting/<uuid:setting_pk>/',
+            # views.admin_user_organization_notification_setting,
+            # name='admin_user_organization_notification_setting',
+        ),
+        path(
+            'user/<uuid:user_id>/organization/<uuid:organization_id>/setting/',
+            views.admin_user_organization_notification_setting,
+            name='admin_user_organization_notification_setting',
+        )
     ]
diff --git a/openwisp_notifications/urls.py b/openwisp_notifications/urls.py
index efc6d2b..3c33306 100644
--- a/openwisp_notifications/urls.py
+++ b/openwisp_notifications/urls.py
@@ -10,7 +10,7 @@ def get_urls(api_views=None, social_views=None):
         api_views(optional): views for Notifications API
     """
     urls = [
-        path('api/v1/notifications/notification/', include(get_api_urls(api_views)))
+        path('api/v1/notifications/', include(get_api_urls(api_views)))
     ]
     return urls

openwisp_notifications/api/urls.py

openwisp_notifications/base/views.py

openwisp_notifications/static/openwisp-notifications/js/settings.js

nemesifier

Good progress @Dhanus3133 👍

Please keep in mind that you need to focus on the point of view of the user (user-centered), making sure the UI provides up to date data and guides the user in a way that allows him/her to understand what's going on.

Web notification on the left, email on the right (as in the current notification settings)
Keep in mind web notifications are required for email notifications, therefore the web/email checkbox inputs have work as in the current notification settings (if you disable web, email will be also disabled and when both are disabled, if you enable email, web will be also be enabled)
Type: show verbose_message in the UI, in the API we call this type_label colors
Please reuse CSS classes for colors, titles, form row, etc
Open first org in the UI automatically
Triangle icon: we should have similar icons to reuse
Accordion title of the org: reuse the style of other pages, eg:

Table: reuse styles from any change list page (table headings, table body, table rows, checkbox, etc)
Make sure email and web are tags
Preferences saved message: please change as discussed (fixed place, different logic than notification toast)
Look for drop-in replacements of default checkbox inputs to look more similar to what the UX designers shared (but no execute yet, just look for possible open source options to use)

pandafy

Good work @Dhanus3133! In this review, I primarily focused on the UX/UI. I hope these points would help you progress with this PR

Add link to the notification preference page in the notification widget
Add link to the notification preference page in the UserAdmin
When the API request fails, the user operation should rollback. E.g. if the user disabled the global web notifications and the API request fails, then the UI should flag the checkbox as enabled again.
Add tooltip to the global and organization settings

openwisp_notifications/templates/openwisp_notifications/settings.html

openwisp_notifications/base/views.py

openwisp_notifications/static/openwisp-notifications/css/settings.css

openwisp_notifications/static/openwisp-notifications/js/settings.js

openwisp_notifications/api/permissions.py

pandafy

In our weekly call, we discussed the following changes to the docs

explain the new interaction between default notification settings in the type definition and disabled global notifications in the preference of the user
make sure API docs page is up to date

We also evaluated the feasibility for adding "Notification Settings" button on the UserAdmin. I have attached the git diff below for reference

diff --git a/openwisp_notifications/admin.py b/openwisp_notifications/admin.py
index 0e320be..15636a8 100644
--- a/openwisp_notifications/admin.py
+++ b/openwisp_notifications/admin.py
@@ -10,16 +10,4 @@ Notification = load_model('Notification')
 NotificationSetting = load_model('NotificationSetting')
 
 
-class NotificationSettingInline(
-    NotificationSettingAdminMixin, AlwaysHasChangedMixin, admin.TabularInline
-):
-    model = NotificationSetting
-    extra = 0
-
-    def has_change_permission(self, request, obj=None):
-        return request.user.is_superuser or request.user == obj
-
-
-UserAdmin.inlines = [NotificationSettingInline] + UserAdmin.inlines
-
 _add_object_notification_widget()
diff --git a/openwisp_notifications/templates/admin/openwisp_users/user/change_form_object_tools.html b/openwisp_notifications/templates/admin/openwisp_users/user/change_form_object_tools.html
new file mode 100644
index 0000000..cd2761b
--- /dev/null
+++ b/openwisp_notifications/templates/admin/openwisp_users/user/change_form_object_tools.html
@@ -0,0 +1,6 @@
+{% extends "admin/change_form_object_tools.html" %}
+{% load i18n admin_urls %}
+{% block object-tools-items %}
+    <li><a class="button" href="/notifications/settings/">Notification preferences</a></li>
+    {{ block.super }}
+{% endblock %}

openwisp_notifications/api/serializers.py

openwisp_notifications/tasks.py

nemesifier

Notes from today's weekly meeting:

Handling of API errors: the UI should not wait for succesful response to update itself, it should just rollback in case of errors
Switch Input Chekbox: we can use this solution (we need to make the :focus more evident and ajust the colors): https://www.w3schools.com/howto/howto_css_switch.asp

nemesifier

update notification preferences button in user page to link the correct URL
notification preferences of another user should show the username in the first heading of the page, please do not change the top right header as discussed
in the notification widget, please change "settings" to "preferences"
once we are done we will need to update the docs

- Updated the `NotificationSettingSerializer` to also include `organization_name`. - New endpoint `/api/user-setting/organization/<uuid:organization_id>/` to allow changes toggling of email/web notification settings of a particular org with just a single API call.

openwisp_notifications/api/views.py

pandafy · 2024-09-06T17:25:36Z

openwisp_notifications/api/views.py

+    def get(self, request, user_id):
+        notification_settings, created = NotificationSetting.objects.get_or_create(
+            user_id=user_id,
+            organization=None,
+            type=None,
+            defaults={'email': True, 'web': True},
+        )
+        serializer = self.get_serializer(notification_settings)
+        return Response(serializer.data, status=status.HTTP_200_OK)


IIRC, we decided that we would make a migration file that would create global notification setting. I don't think, we would need create notification settings on the fly here.

Let me know if i missed on something.

I don't see a migration file in the PR. So, the current implement looks good.

@nemesifier what do you think about this?

pandafy · 2024-09-06T17:48:23Z

openwisp_notifications/api/filters.py

+
+    @property
+    def qs(self):
+        parent_qs = super().qs
+        return parent_qs.exclude(organization__isnull=True, type__isnull=True)


Why did you exclude the global notifications from here? This means that these settings will not appear when the user browse the NotificationSettingListView API endpoint from the browser. Thus, it makes impossible to turn off global notifications using the REST API.

We already have a seperate endpoint to update the global notification settings here

openwisp-notifications/openwisp_notifications/api/urls.py

Lines 53 to 57 in 9661ae6

path(

'user/<uuid:user_id>/preference/',

views.notification_preference,

name='notification_preference',

),

Thinking out loud: What are the benefits of having a separate endpoint for only managing global notifications?

openwisp_notifications/api/views.py

nemesifier

Notes from last round of testing during our weekly meeting:

Fix exception when deleting user (write a failing test first please)

Added by @pandafy: Fix string representation of global NotificationSetting
In the test "test_post_migration_handler", add assertions to verify that global settings are being created

Added by @pandafy: Update test_post_migration_handler in test_notification_settings.py.
Delete the global notifications settings after creating the user.
Call the notification_type_registered_unregistered_handler function
and then assert that global notification setting is created.
Add validation in the model to ensure there can be only 1 global setting for each user
Let's use only 1 endpoint for notification settings
Remove the CSS transition from the arrow in the accordion of the UI

… test

- Removed preference api endpoint and just used the `/user-setting` endpoint. - Fixed some bugs in preference page for handling few cases like enabling of global web setting when any one email setting is turned on (toggles it off). - Handled validation of only one global setting per user in model level.

pandafy

Good progress @Dhanus3133 👏🏼 With these last few improvements, we will get this PR ready to merge.

@nemesifier what will be the best way to convey that there was an error loading the notification settings. There's a toast message which notifies that there was an error but the toast is not persistent. Shall we add a paragraph element conveying that there was an error?

pandafy · 2024-09-09T11:00:43Z

openwisp_notifications/api/views.py

+            for notification_setting in notification_settings:
+                notification_setting.email = validated_data.get(
+                    'email', notification_setting.email
+                )
+                notification_setting.web = validated_data.get(
+                    'web', notification_setting.web
+                )
+            NotificationSetting.objects.bulk_update(
+                notification_settings, ['email', 'web']
+            )


I apologise, my previous comment was misleading. I meant to suggest update instead of bulk_update. So, the code would become:

Suggested change

for notification_setting in notification_settings:

notification_setting.email = validated_data.get(

'email', notification_setting.email

)

notification_setting.web = validated_data.get(

'web', notification_setting.web

)

NotificationSetting.objects.bulk_update(

notification_settings, ['email', 'web']

)

NotificationSetting.objects.update(

email=validated_data['email'],

web=validated_data['web'],

)

openwisp_notifications/tests/test_notification_setting.py

pandafy · 2024-09-16T11:14:33Z

openwisp_notifications/api/views.py

+    def post(self, request, user_id, organization_id):
+        notification_settings = NotificationSetting.objects.filter(
+            organization_id=organization_id, user_id=user_id
+        )
+        serializer = self.get_serializer(data=request.data)
+        if serializer.is_valid():
+            validated_data = serializer.validated_data
+            web = validated_data.get('web')
+            email = validated_data.get('email')
+
+            for notification_setting in notification_settings:
+                if web and not email:
+                    notification_setting.web = web
+                else:
+                    notification_setting.web = web
+                    notification_setting.email = email
+
+            NotificationSetting.objects.bulk_update(
+                notification_settings, ['web', 'email']
+            )
+            return Response(status=status.HTTP_200_OK)
+        return Response(serializer.errors, status=status.HTTP_400_BAD_REQUEST)


Suggested change

def post(self, request, user_id, organization_id):

notification_settings = NotificationSetting.objects.filter(

organization_id=organization_id, user_id=user_id

)

serializer = self.get_serializer(data=request.data)

if serializer.is_valid():

validated_data = serializer.validated_data

web = validated_data.get('web')

email = validated_data.get('email')

for notification_setting in notification_settings:

if web and not email:

notification_setting.web = web

else:

notification_setting.web = web

notification_setting.email = email

NotificationSetting.objects.bulk_update(

notification_settings, ['web', 'email']

)

return Response(status=status.HTTP_200_OK)

return Response(serializer.errors, status=status.HTTP_400_BAD_REQUEST)

def post(self, request, user_id, organization_id):

serializer = self.get_serializer(data=request.data)

if serializer.is_valid():

validated_data = serializer.validated_data

web = validated_data['web']

email = validated_data['email']

NotificationSetting.objects.filter(

organization_id=organization_id, user_id=user_id

).update(web=web, email=email)

return Response(status=status.HTTP_200_OK)

return Response(serializer.errors, status=status.HTTP_400_BAD_REQUEST)

This way, we won't need to iterate over individual objects.

I used validated_data['web'] instead of validated_data.get('web') because NotificationSettingUpdateSerializer requires web and email fields to be present in valid payload.

After another review, I came to conclusion that we don't need to make any changes to the serializer. Please make changes to the test for this endpoint as requested in my previous review. We will see if something breaks because this change.

openwisp_notifications/tests/test_notifications.py

openwisp_notifications/static/openwisp-notifications/js/preferences.js

openwisp_notifications/tests/test_admin.py

openwisp_notifications/tests/test_api.py

openwisp_notifications/tests/test_selenium.py

openwisp_notifications/tests/test_utils.py

openwisp_notifications/views.py

openwisp_notifications/tests/test_selenium.py

openwisp_notifications/templates/admin/openwisp_users/user/change_form_object_tools.html

pandafy · 2024-09-17T16:34:22Z

openwisp_notifications/api/views.py

+    def post(self, request, user_id, organization_id):
+        notification_settings = NotificationSetting.objects.filter(
+            organization_id=organization_id, user_id=user_id
+        )
+        serializer = self.get_serializer(data=request.data)
+        if serializer.is_valid():
+            validated_data = serializer.validated_data
+            web = validated_data.get('web')
+            email = validated_data.get('email')
+
+            for notification_setting in notification_settings:
+                if web and not email:
+                    notification_setting.web = web
+                else:
+                    notification_setting.web = web
+                    notification_setting.email = email
+
+            NotificationSetting.objects.bulk_update(
+                notification_settings, ['web', 'email']
+            )
+            return Response(status=status.HTTP_200_OK)
+        return Response(serializer.errors, status=status.HTTP_400_BAD_REQUEST)


After another review, I came to conclusion that we don't need to make any changes to the serializer. Please make changes to the test for this endpoint as requested in my previous review. We will see if something breaks because this change.

pandafy · 2024-09-17T16:41:42Z

openwisp_notifications/base/models.py

+            try:
+                original = self.__class__.objects.get(pk=self.pk)
+                if self.web and (self.email == original.email):
+                    self.user.notificationsetting_set.exclude(pk=self.pk).update(
+                        web=self.web
+                    )
+                else:
+                    self.user.notificationsetting_set.exclude(pk=self.pk).update(
+                        web=self.web, email=self.email
+                    )
+            except self.__class__.DoesNotExist:
+                pass
        return super().save(*args, **kwargs)


What are the drawbacks for upgrading the NotificationSetting using update()

self.user.notificationsetting_set(web=self.web, email=self.email)

What case would be left uncovered? Can you demonstrate that with a failing test case?

I have added a failing testcase for this

openwisp-notifications/openwisp_notifications/tests/test_api.py

Lines 850 to 870 in a796372

with self.subTest(

'Update organization-level web to False while keeping one of email notification setting to true'

):

url = self._get_path(

'organization_notification_setting',

self.admin.pk,

org.pk,

)

# Set the default type notification setting's email to True

NotificationSetting.objects.filter(

user=self.admin, organization_id=org.pk, type='default'

).update(email=True)

response = self.client.post(url, data={'web': True, 'email': False})

self.assertTrue(

NotificationSetting.objects.filter(

user=self.admin, organization_id=org.pk, type='default', email=True

).exists()

)

Also did add for the global setting here

openwisp-notifications/openwisp_notifications/tests/test_notification_setting.py

Lines 292 to 307 in a796372

with self.subTest(

'Update global web to False while ensuring at least one email setting is True'

):

# Set the default type notification setting's email to True

NotificationSetting.objects.filter(

user=admin, organization=org, type='default'

).update(email=True)

global_setting.web = True

global_setting.save()

self.assertTrue(

NotificationSetting.objects.filter(

user=admin, organization=org, email=True, type='default'

).exists()

)

Let me know what do you think about this.

I commented out the code in question, but the added test didn't fail. :(

I was expecting the test to fail without the added logic.

openwisp_notifications/base/models.py

openwisp_notifications/tests/test_notifications.py

pandafy · 2024-09-18T14:46:19Z

openwisp_notifications/tests/test_api.py

+        with self.subTest(
+            'Update organization-level web to False while keeping one of email notification setting to true'
+        ):
+            url = self._get_path(
+                'organization_notification_setting',
+                self.admin.pk,
+                org.pk,
+            )
+
+            # Set the default type notification setting's email to True
+            NotificationSetting.objects.filter(
+                user=self.admin, organization_id=org.pk, type='default'
+            ).update(email=True)
+
+            response = self.client.post(url, data={'web': True, 'email': False})
+
+            self.assertTrue(
+                NotificationSetting.objects.filter(
+                    user=self.admin, organization_id=org.pk, type='default', email=True
+                ).exists()
+            )
+


This is the scenario which I think this test emulates:

Starting state:

NotificationSetting.objects.filter( user=self.admin, organization_id=org.pk, type='default' ).update(email=True)

state:

Turning off email notifications for the organization:

response = self.client.post(url, data={'web': True, 'email': False})

Contradictory to the UI

self.assertTrue( NotificationSetting.objects.filter( user=self.admin, organization_id=org.pk, type='default', email=True ).exists() )

The UI shows that all email notifications for the organization is disabled, which is correct. But, the test expects the one email notification to stay enabled.

Do I understand the test correctly?

pandafy

@Dhanus3133 update the code (including tests) to call the full_clean model method before calling save on an individual object.

Django does not perform any validation if you save the object directly. The validation is performed in full_clean, hence it is required to call the method before save.

Dhanus3133 changed the base branch from master to gsoc24 July 15, 2024 16:55

nemesifier reviewed Jul 16, 2024

View reviewed changes

nemesifier reviewed Jul 19, 2024

View reviewed changes

openwisp_notifications/api/urls.py Outdated Show resolved Hide resolved

Dhanus3133 force-pushed the notification-preferences branch from bc59840 to f79ad0f Compare August 2, 2024 14:23

Dhanus3133 marked this pull request as ready for review August 4, 2024 15:51

nemesifier requested changes Aug 6, 2024

View reviewed changes

pandafy requested changes Aug 13, 2024

View reviewed changes

pandafy reviewed Aug 13, 2024

View reviewed changes

openwisp_notifications/api/permissions.py Outdated Show resolved Hide resolved

pandafy requested changes Aug 13, 2024

View reviewed changes

openwisp_notifications/api/serializers.py Outdated Show resolved Hide resolved

openwisp_notifications/tasks.py Outdated Show resolved Hide resolved

Dhanus3133 force-pushed the notification-preferences branch from 50bb6c5 to 8f0a703 Compare August 19, 2024 18:08

Dhanus3133 force-pushed the gsoc24 branch from 75edfbe to e4a1d7e Compare August 19, 2024 18:10

nemesifier mentioned this pull request Aug 20, 2024

[feat] Implement global notification setting for email/web #284

Closed

nemesifier requested changes Aug 20, 2024

View reviewed changes

Dhanus3133 force-pushed the notification-preferences branch from c16b203 to bd91c96 Compare August 21, 2024 06:52

Dhanus3133 changed the base branch from gsoc24 to gsoc24-rebased August 21, 2024 06:54

Dhanus3133 force-pushed the notification-preferences branch from bd91c96 to c16b203 Compare August 21, 2024 07:07

Dhanus3133 changed the base branch from gsoc24-rebased to gsoc24 August 21, 2024 07:08

Dhanus3133 and others added 11 commits August 21, 2024 12:41

[chore] Add tests

7016f86

[chore] Use GenericAPIView

6d410fc

[refactor] URL routes

e6cbb9c

[chore] Update tests

531acda

[chore] Add Global Notification

2dfc5a8

[chore] Global Notification Preference changes

215118b

[feat] Notification Settings Page

90221ca

[ci] Run builds for gsoc24 branch

64fe873

[qa] Check fixes

fdb8fdf

[chore] Notification settings page with breadcrumbs

7c5cbeb

Dhanus3133 added 4 commits September 6, 2024 18:43

[chore] Add selenium test

d1c5215

[fix] Tests

082c967

[fix] Tests

c0b7357

[fix] Tests

6106f9b

pandafy requested changes Sep 6, 2024

View reviewed changes

Dhanus3133 added 6 commits September 7, 2024 13:58

[fix] Tests

234627e

[fix] Should fix Tests

3d53083

[chore] Bump changes

9661ae6

[chore] Reuse serializer

0ecaa74

[chore] Increase waiting time for selenium tests

4ec65b7

[chore] Update preference page org dropdown icon position

b9d62b4

nemesifier requested changes Sep 10, 2024

View reviewed changes

Dhanus3133 added 6 commits September 11, 2024 18:37

[fix] Error displaying __str__ for global notification setting

baa6111

[chore] Verify global setting creation in test_post_migration_handler…

c10952e

… test

[chore] Remove transition on accordion

7efa79e

[chore] Update tests

0e687b4

[fix] Import error

5413859

pandafy reviewed Sep 16, 2024

View reviewed changes

pandafy requested changes Sep 16, 2024

View reviewed changes

pandafy requested changes Sep 17, 2024

View reviewed changes

pandafy reviewed Sep 17, 2024

View reviewed changes

openwisp_notifications/tests/test_notifications.py Outdated Show resolved Hide resolved

[chore] Bump changes

a796372

pandafy reviewed Sep 18, 2024

View reviewed changes

Dhanus3133 added 3 commits September 20, 2024 16:20

[chore] Update org level changes

c3f01e5

[chore] Use full_clean instead of saving directly

ad8ff56

[chore] Update global notification setting changes

6c53bf6

Dhanus3133 force-pushed the notification-preferences branch from f1b81f1 to 6c53bf6 Compare September 20, 2024 15:19

[chore] UI changes

2836bbd

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[feat] Notification Preferences Page #290

[feat] Notification Preferences Page #290

Dhanus3133 commented Jul 15, 2024 •

edited

Loading

nemesifier left a comment

nemesifier left a comment

pandafy left a comment •

edited by Dhanus3133

Loading

pandafy left a comment •

edited

Loading

nemesifier left a comment

nemesifier left a comment

pandafy Sep 6, 2024

pandafy Sep 6, 2024

pandafy Sep 6, 2024

Dhanus3133 Sep 7, 2024 •

edited

Loading

pandafy Sep 9, 2024

nemesifier left a comment •

edited by pandafy

Loading

pandafy left a comment

pandafy Sep 9, 2024

pandafy Sep 16, 2024

pandafy Sep 16, 2024

pandafy Sep 17, 2024

pandafy Sep 17, 2024

pandafy Sep 17, 2024

Dhanus3133 Sep 18, 2024

pandafy Sep 18, 2024

pandafy Sep 18, 2024 •

edited

Loading

pandafy left a comment

	path(
	'user/<uuid:user_id>/preference/',
	views.notification_preference,
	name='notification_preference',
	),

	with self.subTest(
	'Update organization-level web to False while keeping one of email notification setting to true'
	):
	url = self._get_path(
	'organization_notification_setting',
	self.admin.pk,
	org.pk,
	)

	# Set the default type notification setting's email to True
	NotificationSetting.objects.filter(
	user=self.admin, organization_id=org.pk, type='default'
	).update(email=True)

	response = self.client.post(url, data={'web': True, 'email': False})

	self.assertTrue(
	NotificationSetting.objects.filter(
	user=self.admin, organization_id=org.pk, type='default', email=True
	).exists()
	)

	with self.subTest(
	'Update global web to False while ensuring at least one email setting is True'
	):
	# Set the default type notification setting's email to True
	NotificationSetting.objects.filter(
	user=admin, organization=org, type='default'
	).update(email=True)

	global_setting.web = True
	global_setting.save()

	self.assertTrue(
	NotificationSetting.objects.filter(
	user=admin, organization=org, email=True, type='default'
	).exists()
	)

[feat] Notification Preferences Page #290

Are you sure you want to change the base?

[feat] Notification Preferences Page #290

Conversation

Dhanus3133 commented Jul 15, 2024 • edited Loading

nemesifier left a comment

Choose a reason for hiding this comment

nemesifier left a comment

Choose a reason for hiding this comment

pandafy left a comment • edited by Dhanus3133 Loading

Choose a reason for hiding this comment

pandafy left a comment • edited Loading

Choose a reason for hiding this comment

nemesifier left a comment

Choose a reason for hiding this comment

nemesifier 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

Dhanus3133 Sep 7, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

nemesifier left a comment • edited by pandafy Loading

Choose a reason for hiding this comment

pandafy 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

pandafy Sep 18, 2024 • edited Loading

Choose a reason for hiding this comment

pandafy left a comment

Choose a reason for hiding this comment

Dhanus3133 commented Jul 15, 2024 •

edited

Loading

pandafy left a comment •

edited by Dhanus3133

Loading

pandafy left a comment •

edited

Loading

Dhanus3133 Sep 7, 2024 •

edited

Loading

nemesifier left a comment •

edited by pandafy

Loading

pandafy Sep 18, 2024 •

edited

Loading