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
feat(router): add logic to router to handle meta tags #216
Conversation
// Use meta property on route to override meta tag defaults | ||
// meta: { title: 'Police Data Accessibility Project - Search', metaTags: [{ property: 'og:title', title: 'Police Data Accessibility Project - Search' }] }, |
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.
Hey @josh-chamberlain just wanted to call your attention to this. We can override any meta tag by route (in absence of specific route data, we fall back to the defaults). So if there are any of them that should have specific values, let me know and I can add those here as well.
Add support for multiple matched routes
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.
lgtm!
@joshuagraber thanks! I'm good to merge this into |
Sounds good @josh-chamberlain changed the base branch, just need another ✅ to merge. |
Will handle #199 when merged.
To test
Run the app, visit several different routes, ensure that the tags change as expected per route (only the
og:url
tag will change for now, but we can use themeta
property on the routes object to update others if need be)