- A message is displayed when the transaction list is not available.
- The transaction list is loaded after the block data.
- When the paginated transactions aren't available, the transaction
list from the block data is displayed.
transactions for the block are now retrieved separately, the
transactions table is paginated and shows more info and
finally the view now is mobile friendly
In order to keep the database in sync, the address
checks are being disabled, this is a partial solution
to let the explorer continue working until the actual
validations are added.
The SQS seeder and the Poller seeder are removed, they weren't
adapted to the linear synchronization process and they are not
required anymore.
Also, all related classes and dependencies that where used by
these tasks were removed too.
The task runs frequently polling the xsn service for its latest block,
then, it calls the LedgerSynchronizerService to ensure that block
gets into the ledger database.
This is a simplified version of the BlockEventProcessor, it handles
the synchronization between the xsn and our ledger database, it also
takes care of a lot of corner cases to keep the synchronization process
flexible enough and linear.
transactions from the address are now retrieved separately, the address
model was chaged for the balance model, the transactions table now is
paginated and shows more info and now the view is mobile friendly
Now it retrieves the address balance from the database
instead of the xsn server, this reduces the data because
now we get the balance only and the transactions are retrieved
with another endpoint.
In order to get deterministic results while retrieving
paginated results, the getUniqueColumnName method has been
introduced, when sorting by a non-unique column, we'll break
ties using the unique column.
Alexis Hernandez
Mario Mejia