Rethink inclusion of `season` top-level field
Behold3th opened this issue · 3 comments
Currently, season is a top level field for bounties that marks the season a bounty was created in.
https://github.com/BanklessDAO/discord-bots : CreateNewBounty.ts
As we migrate to multi-tenancy, we expect customers to not have consistent seasons with BanklessDAO. As well, customers may not use seasons or a similar concept.
The field is helpful for our analytics shareholders, however, the season number can be computed by performing a range query with ISO 8601 date-time values. Thus we have redundant data in our source of truth, which can lead to state invalidation.
Explicitly using the season field would require collection of season and date information from customers, and updating our customers collection with this information for each new season a customer would experience (since it's not guaranteed that seasons have equal lengths). It is also an unnecessary stressor on our go-to-market.
I recommend we remove storing the season field as part of our bounty data.
Assuming we are in a v0.x I would support this breaking change. Having fields unique to Bankless is going to cause technical debt as we deploy across tenants. To my knowledge, this feature is not heavily used.
Closing as the field is now deprecated