Implement Add and Remove Contacts Integration & Fix Lightning History

[basim-12]

@todo

• Implement Add and Remove Contacts Integration & Fix Lightning History
  • Updated Lightning history to visually indicate expired and failed transactions
  • Removed amount prefixes from expired transactions
  • Added a getValue method to read input values outside the shadow DOM
  • Rebuilt the add contact form with Name, Address, and Note fields
  • Styled the add contact form
  • Connected the save button to submit form data via callback
  • Integrated the contact_add API into the contacts list
  • Added contact deletion using the contact_delete API
  • Implemented contact list refresh after add and delete actions
  • Fixed a STATE validation error in the contact form module
  • Added notifications for contact actions
  • Debug and Testing
  • @output 📦 Flamingo-ui Repo commitFrom Comment

[basim-12]

Tasks

• Updated Lightning history to visually indicate expired and failed transactions - 1hr 10min
• Removed amount prefixes from expired transactions - 15min
• Added a getValue method to read input values outside the shadow DOM - 25min
• Rebuilt the add contact form with Name, Address, and Note fields - 25min
• Styled the add contact form - 40min
• Connected the save button to submit form data via callback - 30min
• Integrated the contact_add API into the contacts list - 1hr 35min
• Added contact deletion using the contact_delete API - 1hr 20min
• Implemented contact list refresh after add and delete actions - 30min
• Fixed a STATE validation error in the contact form module - 40min
• Added notifications for contact actions - 40min
• Debug and Testing - 2hr
• Create issue and Worklog - 25min
  • @output 📦 Flamingo-ui Repo commit

Worklog

Add and Remove Contacts Integration & Fix Lightning History

Proposal

[ninabreznik]

@basim-12 Thanks so much, this all looks very nice. I like how now expired transactions are clearly visible and tagged and I also like the adding of new contacts. Makes sense you updated UI to match the backend. maybe we'll even leave it as it is, but if changes will be needed later, we can still update it.

Now to the UI for the multiple nodes. I honestly didn't plan multiple nodes support for the first release, but since we have it in the backend it is actually trivial to add it also in the UI. I actually always liked your slide in/out side pannel to choose the node from. Maybe we could add the same to our existing UI. This way we have the option for testing and if it will feel nice, we can even keep it. What do you think? We would just need an icon to indicate that. If you have any suggestions, please make a proposal.

[basim-12]

@basim-12 Thanks so much, this all looks very nice. I like how now expired transactions are clearly visible and tagged and I also like the adding of new contacts. Makes sense you updated UI to match the backend. maybe we'll even leave it as it is, but if changes will be needed later, we can still update it.

Now to the UI for the multiple nodes. I honestly didn't plan multiple nodes support for the first release, but since we have it in the backend it is actually trivial to add it also in the UI. I actually always liked your slide in/out side pannel to choose the node from. Maybe we could add the same to our existing UI. This way we have the option for testing and if it will feel nice, we can even keep it. What do you think? We would just need an icon to indicate that. If you have any suggestions, please make a proposal.

@ninabreznik Thank you, I am glad you liked all of it, for the UI of multiple nodes I can definitely add the same slide in/out UI, and if we like it we can keep it, I work on it and share it in the worklog soon.