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

UI Changes to make better Metadata for the Validators #95

Open
jflowers1974 opened this issue Dec 1, 2018 · 0 comments
Open

UI Changes to make better Metadata for the Validators #95

jflowers1974 opened this issue Dec 1, 2018 · 0 comments

Comments

@jflowers1974
Copy link

There needs to be more error trapping and explicitly defined fields.

Whilst reviewing https://validators.poa.network/ for myself, I saw a number of mistakes/issues (screen shots upon request - however, if you just look you too will see these.) I too had an issue initially during Network roll as a member of the Trinity Validator Set. I believe my issue was whether or not to use a comma or semi-semicolon to separate fields.

There were obviously bigger issues in those days. However, the issues that I’m seeing are probably fixed with a small cleanup of the UI. I think having explicitly defined fields such as:

Address 1, Address 2, City, State (Drop down), ZIP, USA (automatically appended due to current requirement - but there for completeness):

img_4341

Furthermore - I actually think that we ought to hook in a third party API to check and perhaps suggests an address after the user submits there work. Should the individual not take the requirement - I’d like to suggest the idea of presenting the one that the individual provided AND the API for all to see.

In the case of a minor issue, I fully expect a reasonable individual to understand. But if there’s a ‘larger’ issue - again, I trust in the individual reviewing the data to come to their own conclusions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant