Skip to content
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

Transaction History Design #148

Closed
faboweb opened this issue Dec 1, 2017 · 3 comments
Closed

Transaction History Design #148

faboweb opened this issue Dec 1, 2017 · 3 comments
Assignees
Labels
design-work-needed 🎨 issues that require design work before development

Comments

@faboweb
Copy link
Collaborator

faboweb commented Dec 1, 2017

Current UI:
image

Wasn't there already a more sophisticated design by Peng?

@faboweb faboweb added the design-work-needed 🎨 issues that require design work before development label Dec 1, 2017
@jbibla
Copy link
Collaborator

jbibla commented Dec 1, 2017

  1. is this using the same component (and same design) as the delegate table?
  2. it's missing a bunch of data from Transaction History #22 right?

@nylira
Copy link
Contributor

nylira commented Dec 4, 2017

There isn't a more sophisticated design. I haven't had time to work on it. This is the current design for the transactions page.

@jolesbi

  1. This is using a custom, ancient component CardTransaction -- I think it has to be custom because there are different fields involved.
  2. CardTransaction has to be updated, but I don't think it's missing a bunch of data. I think the only thing that's missing is the address or contact that the tokens is being sent from/sent to. Do you guys think we should show more data? I think that's enough.

The data from #22 should appear on individual transaction pages, which haven't been designed yet.

I can work on these issues this week.

@faboweb
Copy link
Collaborator Author

faboweb commented Dec 4, 2017

+1 on showing sender/receiver.

@jolesbi We will show multiple senders/receivers when it is fully integrated in the SDK (it isn't right now). I will ask about multiple denominations.

faboweb added a commit that referenced this issue Jun 2, 2020
* fixed a bug where a single proposal would not load (#125)

* trigger ci

* fixed missing terra data source (#128)

* Fabo/fix missing terra db query (#130)

* fixed missing terra data source

* fixed missing query

* Fabo/fix failing staking query for terra (#132)

* fixed missing terra data source

* fixed missing query

* fix bech32 prefix in selfStake resolver

* linted

* Fabo/hide proposals on terra (#134)

* fixed missing terra data source

* fixed missing query

* fix bech32 prefix in selfStake resolver

* linted

* don't show proposals on terra

* Fabo/switch to yarn (#122)

* switch to yarn

* Update Readme

* Ana/111 regen testnet production (#118)

* regen is home

* fix websocket link

* eslint fix

* delete console logs

* fixed regen source (using cosmosV0)

* add feature flags for regen

* fix txs in regen

* fix transactions per address

* fix eslint errors

* disable sign in

* colw/Transaction Service (#120)

* Obtain transaction payload, mirror back to client

* Respond with request, or error if none present

* Load node friendly versions of cosmos-api for dev

* Send response as JSON

* Successfully retrieve a gas estimate

- Use node-fetch for cosmosAPIs
-

* Add two sub routes: /estimate and /broadcast

* Add account number and sequence to overview query

* Disable cors options

* Add support to broadcast messages

* Ignore fetch undefined

* Delete package-lock.json

* Fabo/simplify queries (#108)

* simplified db queries

Conflicts:
	lib/luniedb-source.js
	lib/queries.js

* switched to yarn

* clean up

* clean up

* Copy cosmos libraries into container (#143)

* Aleksei/terra url change (#144)

* terra url changed

* change soju-0010 to soju-0012

* fixed db queries (#147)
faboweb pushed a commit that referenced this issue Jun 2, 2020
* add lunie api env variable check

* changelog

* lint
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design-work-needed 🎨 issues that require design work before development
Projects
None yet
Development

No branches or pull requests

3 participants