You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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):
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.
The text was updated successfully, but these errors were encountered:
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):
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.
The text was updated successfully, but these errors were encountered: