Skip to content
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

Prune the catch-all Error type in the client crate #9

Open
hdevalence opened this issue Apr 27, 2023 · 1 comment
Open

Prune the catch-all Error type in the client crate #9

hdevalence opened this issue Apr 27, 2023 · 1 comment
Labels

Comments

@hdevalence
Copy link
Member

The client crate has a giant catch-all Error type, many of whose variants are unnecessary now.

For each variant, we should check if it is ever constructed (eg using vs code) and delete it if not.

@erwanor erwanor moved this to Future in Testnets Apr 28, 2023
@plaidfinch plaidfinch moved this from Future to Next in Testnets May 5, 2023
@plaidfinch plaidfinch moved this from Next to Testnet 53: Himalia in Testnets May 12, 2023
@redshiftzero redshiftzero moved this from Testnet 53: Himalia to Next in Testnets May 26, 2023
@conorsch
Copy link
Contributor

Sounds like a fairly straightforward task. Keeping in Next, so we can perform this cleanup ahead of upcoming audits.

@aubrika aubrika moved this from Next to Testnet 64: Titan in Testnets Oct 18, 2023
@aubrika aubrika assigned conorsch and unassigned conorsch Oct 19, 2023
@aubrika aubrika added this to Penumbra Oct 30, 2023
@aubrika aubrika moved this to 🗄️ Backlog in Penumbra Oct 30, 2023
@aubrika aubrika moved this from 🗄️ Backlog to 📝 Todo in Penumbra Oct 30, 2023
@aubrika aubrika moved this from 📝 Todo to 🗄️ Backlog in Penumbra Nov 16, 2023
@erwanor erwanor moved this from Testnet 64: Titan to Next in Testnets Jan 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Backlog
Status: Next
Development

No branches or pull requests

2 participants