stacker.news/fragments
ekzyis b379e7467f
Territory transfers (#878)
* Allow founders to transfer territories

* Log territory transfers in new AuditLog table

* Add territory transfer notifications

* Use polymorphic AuditEvent table

* Add setting for territory transfer notifications

* Add push notification

* Rename label from user to stacker

* More space between cancel and confirm button

* Remove AuditEvent table

The audit table is not necessary for territory transfers and only adds complexity and unrelated discussion to this PR.

Thinking about a future-proof schema for territory transfers and how/what to audit at the same time made my head spin.

Some thoughts I had:

1. Maybe using polymorphism for an audit log / audit events is not a good idea

Using polymorphism as is currently used in the code base (user wallets) means that every generic event must map to exactly one specialized event.

Is this a good requirement/assumption? It already didn't work well for naive auditing of territory transfers since we want events to be indexable by user (no array column) so every event needs to point to a single user but a territory transfer involves multiple users.

This made me wonder: Do we even need a table? Maybe the audit log for a user can be implemented using a view? This would also mean no data denormalization.

2. What to audit and how and why?

Most actions are already tracked in some way by necessity: zaps, items, mutes, payments, ...

In that case: what is the benefit of tracking these things individually in a separate table?

Denormalize simply for convenience or performance? Why no view (see previous point)? Use case needs to be more clearly defined before speccing out a schema.

* Fix territory transfer notification id conflict

* Use include instead of two separate queries

* Drop territory transfer setting

* Remove trigger usage

* Prevent transfers to yourself
2024-03-05 13:56:02 -06:00
..
blockHeight.js Add block height to price carousel (#484) 2023-09-12 10:56:02 -05:00
chainFee.js Add chain fees to price carousel (#658) 2023-12-20 16:06:22 -06:00
comments.js better link rel attr handling 2024-03-04 19:20:14 -06:00
invites.js better organize user graphql types 2023-11-09 19:05:35 -06:00
items.js better link rel attr handling 2024-03-04 19:20:14 -06:00
notifications.js Territory transfers (#878) 2024-03-05 13:56:02 -06:00
price.js Add proxy with cache for coinbase API requests (#226) 2023-01-27 17:20:33 -06:00
rewards.js allow viewing reward ranges 2023-08-29 19:13:21 -05:00
subs.js Territory notifications for everyone (#870) 2024-02-23 09:12:49 -06:00
users.js Territory notifications for everyone (#870) 2024-02-23 09:12:49 -06:00
wallet.js LND autowithdraw (#806) 2024-02-13 13:17:56 -06:00