-
Notifications
You must be signed in to change notification settings - Fork 112
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
Warning for missing information #616
Comments
Currently a warning 'Some of the data on this page is incomplete, please update the fields marked with "!! to improve data quality.' is shown if a field of record Proposal: do not show this warning for fields
|
+1 |
Small addition after last call. Currently a warning 'Some of the data on this page is incomplete, please update the fields marked with "!! to improve data quality.' is shown if a field of record net is not set. Proposal: do not show this warning for fields
|
Small addition after last call. Currently a warning 'Some of the data on this page is incomplete, please update the fields marked with "!! to improve data quality.' is shown if a field of record net is not set. Proposal: do not show this warning for fields
|
I understand this as: don't show a warning for the fields |
@vegu, that is correct. |
* remove warning for missing information for fields: aka, looking glass server url, route server url (#616) remove warning for missing information for fields: ipv4 prefixes, ipv6 prefixes if either of them is set (#616) * Use autocomplete fields in the admincom controlpanel to speed up loading times (#597) * Better error reporting for POSTs and PUTs (#610) * Add operation to API to look for covering prefixes given an IP (#25)
This is a request on behalf of Vladimir Drushchits (raised during Moscow Peering Forum 2019): "We are an ISP so we consider ourselves a Network and not an IXP in PeeringDB. Our Org object constantly pushes warnings to fill in the routeserver information. As an ISP, network, we do not run a routeserver. Could the warnings stop for networks pls? "
The text was updated successfully, but these errors were encountered: