-
Notifications
You must be signed in to change notification settings - Fork 4
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
Search for pronouns in field values, names and the bio #72
Draft
nachtjasmin
wants to merge
8
commits into
main
Choose a base branch
from
61-search-for-pronounspage-link-in-all-fields
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
With all the new pronouns from all languages we get false positives, such as "I" for https://botsin.space/@lesbianBot. Also logging could be a bit improved - the addon doesn't output any info after fetching a status |
nachtjasmin
force-pushed
the
61-search-for-pronounspage-link-in-all-fields
branch
from
August 1, 2023 13:53
87aef3e
to
abcbadb
Compare
The old approach was refactored. With this commit we are applying all searches to each individual field, including their name and value. This approach is optimized for speed in that regard, that we do the API calls as the last step.
too many false positives for comma
nachtjasmin
force-pushed
the
61-search-for-pronounspage-link-in-all-fields
branch
from
August 14, 2023 12:13
71bb62e
to
907405d
Compare
Although it looks fine to me, I won't merge it unless I've fixed the following problem:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The old approach was refactored. With this PR we are applying all searches to each individual field, including their name and value. This approach is optimized for speed in that regard, that we do the API calls as the last step.
I also embedded a list of all known pronoun.page pronouns, which can be generated using
node scripts/generateKnownPronouns.mjs
. The current state is commited to the repository and could be regenerated at any time.A lot of the cases mentioned in #63 are going to be closed with this PR.