-
Notifications
You must be signed in to change notification settings - Fork 152
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
Feat/taro-update-backend #669
Feat/taro-update-backend #669
Conversation
if (compatibility) { | ||
const requiredVersion = compatibility[lndBackend.version]; | ||
//version compatibility function breaks down | ||
if (!requiredVersion) { |
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.
I had a lot of trouble hitting this if statement, I couldn't figure out how what test you were running where your coverage would clear.
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.
This has been rebased to the latest add-taro.
100% Coverage and linting checked.
What is the process to remove the conflicts with the main branch? Is that something that I do, or would you do?
Also, should I rename any variable named lndName to something like LNDname? I think I remember a note that said something along those lines?
This needs a rebase on master since #656 and #667 were merged. One tip to make rebases a little easier is to do an interactive rebase then drop all of the commits that are already in the base branch. git rebase -i feat/add-taro I did a pass on this to test the UX. I noticed some things to improve:
|
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.
I think this might be the last feature on the addTaro check list.
Coverage, testing and linting 100%.
I added the drag link feature.
Thanks for clarifying this behavior. I'll look into a solution. Sounds like a good challenge. |
Proper casing on the usePrefixedTranslation
Added updateTaroBackendNode and updateTaroBackendLink
Added tarp send asset functionality.
Rebase onto latest add-taro
When dragging from LND network node to a Taro node or vice versa, the Change Taro Backend Modal will appear.
32f8991
to
387e943
Compare
If a node as assets, disable the change taro backend button.
Taro change backend button is only enabled when the network is started and has no assets.
Changing taro backend is only available before the network starts and while a admin.macaron exists. If the macaron exists, and error pops up.
Cleaning up cruft
K this is ready for review. |
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.
Did another pass of the UX and found some issues. Can you resolve these before I dive into code review?
- With
carol-taro
connected tocarol
, drag a new link between the two and click Change Backend. It will display an already connected error, which is correct. But now if you click on the link, the sidebar says invalid selection. You will also see a link remains if you drag fromalice-taro
tobob
then hit Cancel in the modal. You have to remove the temporary link that gets added when dragging. - I am allowed to change the backend of a started network by dragging a link between the nodes. It should display an error
- With the network started, the Change Taro backend modal displays a message stating the node will be restarted automatically. This msg should be removed since we won't allow changing after initial startup. Also remove the code that restarts the node
- I'm getting failing tests in
LinkDetails.spec.tsx
due to this errorNote: to make your life easier, it would be fine to ignore the unit tests for now. When the UX/code are approved and final, then you can write all of the test. I usually implement the full feature first, then write tests at the end, so I don't have to repeated rewrite the tests over and over again while iterating on the code./Users/jamal/dev/polar/src/utils/config.ts:208 join)(network.path, 'volumes', ^ TypeError: Cannot read properties of undefined (reading 'path')
Thanks for the feedback and guidance, I'll get on this. If you are happy with this, Ill move on to cleaning up the tests. |
Links are removed when modal is hidden. Restarting is removed. Change Taro Backend button errors after the network has been started.
I hit these notes, thanks for running through this, this has been a challenging task. |
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.
Functionality looks good now.
Did a first pass of code review.
This should be good for review. |
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.
Apologies for taking a while to review this. I missed your comment about it being ready. I just happened to check today because I was wondering about the status of this PR. In the future, it would be helpful if you can click on the re-request review icon on the PR. I typically check my review queue on a daily basis and it will stay on my list until I review it.
Thanks for the updates. After another pass on the code, there's just a few minor tweaks I'd suggest. Also there were some comments from my prior review that were not addressed. They are the ones not marked as unresolved.
const taroNode = network.nodes.taro.find(n => n.name === taroName) as TarodNode; | ||
const result = await exists(taroNode.paths.adminMacaroon); | ||
setHasMacaroon(result); |
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.
You can run this code in the handleChangeClick
callback instead of adding a state var.
Tests, lint and coverage 100%
Thanks for pointing me to to the re-request review button. I'll be sure to use that in the future. |
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.
Thanks for the updates. I just reiterated a couple comments on the en-US.json
file. Then this should be good to go.
Good to go. |
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.
Perfect 👌
Thanks for iterating on this. Going to squash merge this because there are a lot of commits and the diff is not that big.
Create a draft of this for you to inspect workflow. I'm still working on tests and coverage. Also, compatibility filtering isn't working. I will figure that out.
Description
Modal for changeing the backend of taro nodes.
Steps to Test