-
Notifications
You must be signed in to change notification settings - Fork 10
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
Enhancement/issue 125 meta from config #303
Enhancement/issue 125 meta from config #303
Conversation
this.setMeta(config.meta, currentPage); | ||
} | ||
|
||
setDocoumentTitle(title = '') { |
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.
sp. setDocumentTitle()
titleElement.innerHTML = title; | ||
} | ||
|
||
setMeta(meta = [], currentPage = {}) { |
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 really liked this in a separate component as people will want to do custom app-templates, it would be easier to simply import the metaComponent. Thoughts?
this.setDocoumentTitle(config.title); | ||
} | ||
|
||
setDocoumentTitle(title) { |
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.
sp. setDocumentTitle() or is this on purpose because its reserved or something?
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.
Spelling mistake on function, I don't know if that was intentional. Is it not easier for other developers looking to make their own app-templates if we can refactor the meta query and dom changes into a separate component ?
😬 Good catch. 👍
I think that's definitely a good idea and so I think you are thinking of having something equivalent to react-helmet? I think that's a good idea so unless there's any strong objection, I think I would like to make an issue for that, primarily to determine if
|
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.
* graphql server working * apollo client connect to apollo server * connected header example using lit apollo * todo * todos * query and client + server refactor * schema refactoring * clean up console logging * alias all @greenwood/cli/data module imports * avoid paramater destructuring * graphql example in the header * multiple schemas * internal data sources documentation * shelf refactor and children query integration * refactor out ApolloQuery * ability to intercept client.query calls * basic semi-working implementation * remove extra config from server context * have puppeteer wait for graphql requests before returning content * fix and add test cases for apollo * merged resolvers not actually working * multiple queries support * everything working * todos * TODO tracking * fix fallback apollo client fetch handling * full test suite * cache json test cases * stablize test due to inconsistent data results ordering * clean up deps * todo cleanup * remove forced client call in SSG mode for client * represent graph through the schema * updated data docs * typos and grammer * typos and community link fixes
578031f
to
b5d98ee
Compare
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.
Made a follow up issue for creating a standalone <meta>
component package. 👍
Related Issue
resolves #125 and builds off of / should be merged after #300
Summary of Changes
<meta>
data to app-template.js, like with<title>
and pull from GraphQLMETAELEMENT
,METADATA
,METAIMPORT
href
from config schemaTODO (nice to have)
qql
query?