-
Notifications
You must be signed in to change notification settings - Fork 242
Add "info" field to token pools, consume "symbol" from connectors #606
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Can store contract-specific data that does not map to a top-level token pool field - such as the contract address, name, etc. Signed-off-by: Andrew Richardson <andrew.richardson@kaleido.io>
If an input "symbol" was specified, the returned one must match. If no input "symbol" was specified, the connector may specify anything. Signed-off-by: Andrew Richardson <andrew.richardson@kaleido.io>
Signed-off-by: Andrew Richardson <andrew.richardson@kaleido.io>
Codecov Report
@@ Coverage Diff @@
## main #606 +/- ##
===========================================
- Coverage 100.00% 99.98% -0.02%
===========================================
Files 305 305
Lines 18181 18196 +15
===========================================
+ Hits 18181 18193 +12
- Misses 0 2 +2
- Partials 0 1 +1
Continue to review full report at Codecov.
|
| if ffPool.Symbol == "" { | ||
| ffPool.Symbol = pluginPool.Symbol | ||
| } else if ffPool.Symbol != pluginPool.Symbol { | ||
| return fmt.Errorf("received symbol '%s' does not match requested '%s'", pluginPool.Symbol, ffPool.Symbol) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this is returned (and probably bubbled up to the user), should this be in the translations file? Also, maybe some wording that indicates that what was actually on the blockchain didn't match the API request. Rather than "received" vs "requested"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All the processing in the events module is asynchronous on the event loop, so won't be easily visible to a user except in logs. I can tweak the wording though.
Signed-off-by: Andrew Richardson <andrew.richardson@kaleido.io>
No description provided.