-
Notifications
You must be signed in to change notification settings - Fork 3
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
Delegate to any address #162
Labels
Priority: 🟠 P1
Added to issues and PRs relating to a high severity bugs.
Type: 🏗️ Feature
Added to issues and PRs to identify that the change is a new feature.
Comments
Tbaut
added
Priority: 🟠 P1
Added to issues and PRs relating to a high severity bugs.
Type: 🏗️ Feature
Added to issues and PRs to identify that the change is a new feature.
labels
Sep 24, 2024
in terms of design, I'm thinking of:
|
Aside from search/redirect functionality, the current validation against the registry would need to be changed it seems. I'll have a look. Could you assign me? |
@Tbaut sure no problem. I'll check it out |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Priority: 🟠 P1
Added to issues and PRs relating to a high severity bugs.
Type: 🏗️ Feature
Added to issues and PRs to identify that the change is a new feature.
Feature request from a user:
I want to delegate to any address, and not just from the ones in the list.
Personal opinion: It's a feature request I expected to come eventually. We need to think about it in terms of design. Maybe a button in front of the list? Also we need to adapt the
Delegate/index.tsx
to not error out if the address isn't known.The text was updated successfully, but these errors were encountered: