quokkastake / cosmos-proposals-checker Goto Github PK

v1beta1 proposals are correctly parsed but not v1, need to fix it.

Example: quicksilver

Add a command, like /proposals, that fetches a new state and displays it. Something like:

'''
Cosmos

Proposal #1 - Blablabla

• Wallet xxxx - ✅ (Yes)
• Wallet yyyy - ❌
• Wallet zzzz - ⚠️ (request timeout)

Osmosis

• ⚠️ Could not get proposals: request timeout
  '''

If a request has failed, and a wallet has voted already, then its vote isn't presented in the new state, therefore if a request won't fail next time, it'll spawn a new notification instead. Need to fix.

1. make a config struct inside Chain, called Explorer, with 3 fields, name, wallet link pattern and proposal link pattern
2. if it's not specified, but mintscan prefix is specified, generate an Explorer based on mintscan
3. if Explorer is present, print wallet link instead of displaying it in plaintext

Add a string like "voting ends at 2022-09-16 14:52 (in 3h11m55s)" to reports

Instead of a string, require a struct in config with two fields: address (required), name (optional).
Print wallet alias everywhere instead of address if it's provided.

Use a template engine like ejs, have a template file per each notification type. When rendering a notification, take this template and render it, substituting the notification data.

Change the command to mute to also allow to be run like that:

/proposals_mute 24h cosmos

So it would mute all the alerts on chain.

in strings like Voting ends at: 2023-01-31T20:00:22.143489464Z (in 155h57m33s)

1. pretty format date
2. pretty format duration (with days)

1. display current vote on vote reports (like "Vote: YES")
2. add new report type, REVOTE (and probably refactor to add types, NOT_VOTED/VOTED/REVOTED, only send VOTED/REVOTED to telegram) to send a message like "wallet xxx changed its vote on proposal X on Y: Zzzz. Old vote: A. New vote: B."

Currently when querying for proposals and there's an error in response, it's not respected. Need to parse it correctly and return to client.

Something like "Querying proposal N on F failed: request timeout"