-
Notifications
You must be signed in to change notification settings - Fork 29.4k
feat(Metadata): add support for pinterest meta tag #70873
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
Conversation
Adds the pinterest meta tag allowing you to opt out or in of their rich pin data feature
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.
Agree with the changes.
Hey @ijjk what are the chances of this being looked at? |
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.
Orca Security Scan Summary
Status | Check | Issues by priority | |
---|---|---|---|
![]() |
Secrets | ![]() ![]() ![]() ![]() |
View in Orca |
🔑 The following Secrets have been detected in your pull request across all commits
NAME | FILE | LINE NUM | COMMIT | ||
---|---|---|---|---|---|
![]() |
GCP OAuth Client Secret | ...pp/config/backend.ts | 29 | 484efae | View in code |
![]() |
GCP OAuth Client Secret | ...supertokensConfig.js | 36 | 6852eff | View in code |
![]() |
GCP OAuth Client Secret | ...ith-supertokens/.env | 6 | f6c62d3 | View in code |
![]() |
GCP OAuth Client ID | ...pp/config/backend.ts | 28 | 484efae | View in code |
![]() |
GCP OAuth Client ID | ...supertokensConfig.js | 35 | 6852eff | View in code |
![]() |
GCP OAuth Client ID | ...ith-supertokens/.env | 5 | f6c62d3 | View in code |
I tried removing the changes made to the readme but the pre commit hook didn't allow that, so nothing I can do. |
I can't push changes to this pr, I opened another one to complete the implementation and fix the tests #76988 |
Sounds good! |
Adds support for Pinterest's Rich Pin Data meta tag, while future-proofing for additional Pinterest tags.
This currently works like so
And would resolve to:
Here is pinterests docs on the topic: https://help.pinterest.com/en/business/article/rich-pins