Skip to content
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

Clean up more parse-backticks selectors #4819

Merged
merged 10 commits into from
Oct 1, 2021

Conversation

kidonng
Copy link
Member

@kidonng kidonng commented Sep 25, 2021

Related #4135
We only cleaned up the selectors a little bit in 5e40087 (#4361) but there's plenty more to deal with. I started with removing all "commit" related selector since they should all be native now.

Test URLs

(Too many places 🤷‍♀️ just test and see if there are places left out)

Screenshot

@kidonng kidonng marked this pull request as draft September 25, 2021 11:12
@kidonng kidonng marked this pull request as ready for review September 25, 2021 12:29
@kidonng
Copy link
Member Author

kidonng commented Sep 25, 2021

@yakov116
Copy link
Member

I see you removed some code for the repo search. Please provide a real URL to make sure the issue does not happen.

Comment on lines 20 to 21
'.issues_labeled .text-gray-dark > a', // `isDashboard` "help wanted" event titles (GHE #4021)
'.issues_labeled .color-text-primary > a', // `isDashboard` "help wanted" event titles
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can anyone help with testing if this is still needed?

Unfortunately I don't have any help wanted on the feed at the moment. If you follow me I just added a help wanted label on a RG issue though

Copy link
Member Author

@kidonng kidonng Sep 26, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you follow me I just added a help wanted label on a RG issue though

Of course I'm going to follow you, even if it's not for the label! Again, wondering why I didn't do this before.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Label added, you should see it now

@@ -52,14 +33,6 @@ function init(): void {
parseBackticks(element);
},
});

// `isRepoSearch` might highlight keywords inside backticks, breaking the regular dom-formatter #3509
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see you removed some code for the repo search. Please provide a real URL to make sure the issue does not happen.

👍 Checked and added link to first post. GitHub does it natively now https://github.com/sindresorhus/refined-github/search?q=latest+reliable+button+is%3Aissue&type=Issues

Screen Shot 4

@yakov116
Copy link
Member

yakov116 commented Sep 26, 2021

Added a help wanted

source/features/parse-backticks.tsx Show resolved Hide resolved
@kidonng
Copy link
Member Author

kidonng commented Sep 26, 2021

I see you removed some code for the repo search. Please provide a real URL to make sure the issue does not happen.

I thought I did? Maybe that's another PR, sorry for that 😄

Copy link
Member

@fregante fregante left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good to merge by v21.10.1

@kidonng kidonng marked this pull request as draft September 30, 2021 05:49
It seems titles are mostly parsed by GitHub however commits (especially description) are not.
@fregante
Copy link
Member

I will merge this within 24 hours

@fregante fregante marked this pull request as ready for review October 1, 2021 20:47
@fregante fregante merged commit da2a6db into refined-github:main Oct 1, 2021
@kidonng kidonng deleted the parse-backticks branch January 9, 2022 07:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

3 participants