-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Default Testing network_id to match GanacheUI #1577
Conversation
Should pass tests and build successfully once the leftover v4 test stuff is updated. |
a4712e2
to
eb0c00e
Compare
(I have a reminder to come up with my thoughts on the requirements for this. Will circle back.) |
Following up on this, don't recall why it would be an issue to change the network_id to match GanacheUI's, but I'm probably forgetting something. |
@CruzMolina So did we have any followup thoughts on this? It looks like it might be fine? |
@eggplantzzz This still needs to be smoke-tested. It's been a while, but I believe there are a couple edge cases to consider. Will probably need to document pros/cons of how things work now vs how they work on this branch. |
So, after QAing this branch a bit, I haven't been able to find any bugs for this. Current downsides have been well-documented in #1726. i.e. running
Pinging @gnidan before merging since it seems like he had a thought or two about this. |
Closing this since I believe we don't actually want One possible solution is to have |
Per DavidBurela's feedback: https://twitter.com/DavidBurela/status/1075961475145949185
Defaults
truffle test
to use GanacheUI's default network_id when no network configuration is defined. The network will currently be defined astest
.If it's a must for UX/UI reasons to have the network logged as
ganache
, then probably something along the lines of setting a boolean in options during the workflow and passing that val around will need to be done.