#chanene_webhooks
urban baneBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1268319223986257930
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
visual moss
Do you have an example Event ID I can look at?
lapis wharf
Not at the moment.
visual moss
What are you expecting previous_attributes to contain?
lapis wharf
I expect previous_attributes to contain previous state of the field(s) before they were changed (before this update happened). And usually it does, but for transactions for some reason it doesn't.
Then again most other fields I've seen aren't arrays
Scenario: an auth is updated because a new transaction was captured.
transactions: [{id: ipi_aTransaction01}, {id: ipi_aTransaction02}]
previous_atrributes: [transactions:[{id: ipi_aTransaction01}]]
The previous_atrributes.transactions field has only 1 transction listed, while main transactions field has 2 listed.
visual moss
That seems expected, no? Because there's only 1 transaction that would be considered a previous transaction, while the other would be the current transaction
lapis wharf
Yes that scenario is what I expected to happen, but that's not what's actually happening.
The way it's working currently is both fields have 2 transactions listed.
visual moss
I'm going to need to see an Event link or ID at this point to see what you're seeing
lapis wharf
I'll open support request with an example later then. I just wanted to verify if this was a bug or a feature.
Thank you for your help so far.