Implement the new design of transaction initiation view #4456
Comments
5 tasks
5 tasks
ManuGowda
pushed a commit
that referenced
this issue
Sep 7, 2022
… (#4459) * Add sample chain config * Add connectionCreator utils * Create custom hooks for managing the state * Create connection manager * Add the wcm lib to Lisk Desktop * Update dependencies * Use context to transfer information * Add features to reuse existing components * Abstract BlockchainAppDetailsWrapper out of BlockchainApplicationDetails * Update connection summary and success views according to the design guides * Apply designs to the Connection Proposal view * Implement the design of the pairings list view * Cleanup code and remove logs * Move navigations outside wcm * Break constants into lifeCycle and permissions * Store session data in context object as "session" * Make use of the useSession hook * Fix breaking session request page * Fix default icons * Fix select all accounts * Add unit test coverage to wcm * Add unit test coverage to blockchain application components * Fix failing unit tests * Add missing unit test coverage * Improve tests * Implement the intro page design * Navigate to requestView instead of the intro step * Add multistep and handle navigation * Fix broken unit test * Apply peer-review requested changes * Add multistep and handle navigation * Remove uninted width issue * Apply PR feedback * Remove the connectionHandler component * Add human readable titles
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
As a last and most important step in implementation of the objective, we should create a introductory view that informs the user about the origin of a transaction initiated by another application.
Acceptance Criteria
Additional Information
The logic of receiving the transaction request and signing it is to be implemented by #4418
The text was updated successfully, but these errors were encountered: