-
Notifications
You must be signed in to change notification settings - Fork 192
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
Backend implementation of "detect bugs with similar domain names" #865
Comments
Hi @hallvors: as discussed on IRC, I'll start work from here:
Afterwards, how should I continue? Perhaps work on the frontend to check realtime for matches on the domain name? |
Sounds good! I'd suggest as a next step (on the backend - to complete this bug) creating a new endpoint in api/endpoints.py called domainsearch or something like that, accepting one argument - let's call it q. So webcompat.com/api/domainsearch?q=goog will do a lookup in the DB and return
etc. |
(maybe add url too..limit the hits to 10 or something and make sure in the clientside JS to only start searching when 3-4 letters are entered to avoid a "download the internet" torrent..) |
In the list above I would add a reference to a separate issue on migrating the database for backups, restart of the server, and updating the schema. |
@dshgna do not forget to commit your code modifications in a branch and reference this issue. I see you have already ticked two boxes but I don't see any commits. |
I added the list of tasks to the first comment so We can keep track of completed tasks in cross bugs. |
… to extract domain name
@karlcow: Committed the tasks I've done so far :) |
@dshgna Same comments than the previous PR. Could you avoid large commits with very long commit messages. And do atomic commits. You do not have to push them right away but I would recommend to work on your code in small bits addressing specific section. You will see it's a lot clearer in the future. See for example what I'm doing in |
@karlcow Thanks so much. I will commit so in future commits. I agree it's much more clearer. |
@dshgna said on IRC:
I said yes. So hold on for new comments. |
As mentioned in the PR for this issue, we want to hold off on any more work towards this feature. It's intended to be one of the projects for the Outreachy intern -- thanks. |
Closing for now, please see: #307 (comment) |
This issue is about coding a backend for the feature described in #307
This work can probably start before the design in #307 is ready. It will most likely depend on the issues database created in #788
The text was updated successfully, but these errors were encountered: