-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Refactor conversation-links-on-repo-list
to use selector-observer
#3514
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks right
Actually… it’s not faster. I found out that selector-observer always waits for dom-ready. This sort of limits the usefulness of this package. I wonder if we need to find another package. It makes sense that it waits (for performance reasons) but also this means that features are no longer instant. |
Your right. 😢 https://github.com/josh/selector-observer/blob/master/lib/ready.js I have however found that on Ajax requests or when we were doing observelement on init this was faster. But otherwise it only makes it simpler. |
conversation-links-on-repo-list
conversation-links-on-repo-list
to use selector-observer
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👎 This doesn't seem to have benefits, according to #3084 (comment) — that is, this is not a "ajaxed hot-area"
Thoughts?
I guess this does have |
Congrats on your first merged PR 😸 |
Thanks! |
init | ||
}, { | ||
include: [ | ||
pageDetect.isGlobalSearchResults, | ||
pageDetect.isUserProfileRepoTab |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Duplicate page detect :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel a Lint PR coming
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fregante I am going to send a lint pr but I only have 2 small things. Have any lint in mind??
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you cleanup some feature names?
cleanup
->clean
- rename
add-tags-to-commits
totags-on-commits-list
Also if you want to:
- Ensure descriptions always end with
.
and use the 3rd person (in source or readme). grep/ripgrep or your editor’s search can help - Change all cache durations to be on one line, i.e.
maxAge: {hours: 1}
- Double-check if TODOs have been resolved or can easily be resolved
- Verify whether some
screenshots: false
features could have a screenshot - Check whether features still work, picking some at random or in any order you'd like
Not quite lint, but:
- See if you want to do any of the good first issues, particularly bugs
lint-ideas
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Change all cache durations to be on one line, i.e.
maxAge: {hours: 1}
Haha I made them on new lines since I though it was easier to read
LINKED ISSUES:
Let's make Refined GitHub faster ⚡️ #2671
TEST URLS:
https://github.com/search?q=user%3Asindresorhus+sindre
https://github.com/sindresorhus?tab=repositories&type=source
SCREENSHOT:
None