Skip to content
This repository has been archived by the owner on Jan 24, 2022. It is now read-only.

Fetch last proxy created event to handle recursive proxy creation #367

Merged
merged 1 commit into from
Oct 26, 2018

Conversation

spalladino
Copy link
Contributor

Note that this still leaves the issue that any proxies created from
within a contract will not be tracked by the CLI, and will need to
be manually updated.

Fixes #366

Note that this still leaves the issue that any proxies created from
within a contract will **not** be tracked by the CLI, and will need to
be manually updated.

Fixes #366
@facuspagnuolo facuspagnuolo added the status:on-hold Do not move forward for now label Oct 25, 2018
@facuspagnuolo facuspagnuolo self-assigned this Oct 25, 2018
@facuspagnuolo facuspagnuolo merged commit fdac2c9 into master Oct 26, 2018
@facuspagnuolo facuspagnuolo removed the status:on-hold Do not move forward for now label Oct 26, 2018
@facuspagnuolo facuspagnuolo deleted the fix/fetch-correct-proxy-address-#366 branch October 26, 2018 13:27
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fetch wrong proxy address if initialization involves creating another proxy via App
2 participants