-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Magic field wildcard support #383
Comments
It seems a little confusing because there's an implicit |
Internally yes but it's not visible to the user.
They are set by the providers, not sure how we could normalize them. It could be anything |
Internally it's okay, but how do you explain it to the user: "we have It seems it would be cleaner to do something like we do for cities (removing "city" suffix from "new york city") and remove the common legal form suffixes (or maybe find something even little smarter) so that the returned names look all the same. |
Possible starting point: https://github.com/ProfoundNetworks/company_designator/blob/master/company_designator.yml. E.g.:
|
One remaining problem that I see after checking our data is |
How about we add wildcard support using * ?
It will be useful in cases where there is full match but you dont want it. e.g. There are Zenlayer probes and Zenlayer Inc. probes.
magic:zenlayer will only return 3 probes because it matches them fully.
A good solution would be magic:zenlayer* to match every single probe. Other companies have similar issues because their ASNs are not uniform and use random combinations of their company names.
The text was updated successfully, but these errors were encountered: