You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think we should make UnknownTransactions have all camelCased fields so we can better prepare for when the type is fully supported in helium-js, and avoid re-writing any frontend code (e.g. challenger_owner will eventually have to be updated to challengerOwner)
there are some examples of us doing this with camelCaseKeys() in helium-js
and this may be a separate issue, and I haven't thought it all the way through, but we could probably also convert some or all transactions to automatically return all camelCased keys so that when a new field gets added to hotspot for example, it'll automatically start showing up instead of needing to be manually added to the hotspot definition
The text was updated successfully, but these errors were encountered:
I think we should make UnknownTransactions have all camelCased fields so we can better prepare for when the type is fully supported in helium-js, and avoid re-writing any frontend code (e.g.
challenger_owner
will eventually have to be updated tochallengerOwner
)there are some examples of us doing this with
camelCaseKeys()
in helium-jsand this may be a separate issue, and I haven't thought it all the way through, but we could probably also convert some or all transactions to automatically return all camelCased keys so that when a new field gets added to
hotspot
for example, it'll automatically start showing up instead of needing to be manually added to thehotspot
definitionThe text was updated successfully, but these errors were encountered: