-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Plugin Library build fixes #3906
Conversation
* page path defaults to '/' * Add test
* Check for graymatter excerpt Checks to see if there is a gray-matter excerpt before returning a pruned character count * Fix test Remove a variable that wasn't being used * Create page to describe excerpts * Update using-remark example * Remove package-lock.json * Remove console.log statements * Update copy Updates copy to be a bit more descriptive * Update header for example page * Begin stubbing out extend-node.js tests Created a basic framework for creating a markdown node via the onCreateNode function. This should be expanded to factor in the changes that occur in the setFieldsOnGraphQLNodeType function. * Add query test Adds a test that uses graphql to query a node with its excerpt * Regroup tests Regroups tests so that graphql queries and node tests are in their own groups * Fix linting errors Fixes linting errors that were causing issues on travisCI * Format
* Upgrade style-loader to 0.19.0 to fix webpack-contrib/style-loader#182 * Update to last version
* Updated links for Glamor and Styled Components * Update index.md
* Don't generate pages for test files * Use parsedPath.base instead of path
This reverts commit 834dcb8. A number of people were reporting that this broke the default starter in node 8 e.g. https://twitter.com/Lehanism/status/951397594953076737
* Fix Links Redirection * Fix Glamor Link Redirection
* Cleanup Glamor / Styled Component mini-tutorials * Tweaks
reusabilty => reusability
* Update Deploy Gatsby page - Gitlab Pages Have made a few edits, mainly to include the Path Prefix plugin, which is needed when using Gitlab pages without a custom domain. This has basically been shamelessly copied from the Github pages example... Also did a bit of formatting. * fix typo
* correct key behavior * remove trailing slash logic * remove adding new variable
Add Strata starter to the list.
* update styled-jsx dep in gatsby-plugin-styled-jsx * move styled-jsx to peerDependencies in gatsby-plugin-styled-jsx
@calcsam I added two missing dependencies but looks like building the static html is still failing. Looks like not all the data some of the packages needs is making it's way down after querying, trying to make that a little safer. This error: |
hitsPerPage: 1000, | ||
}) | ||
|
||
// TODO: Currently the gatsby-transformer-remark plugin |
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 needs fixed
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.
@KyleAMathews I pulled this out and found the problem packages, in terms of fixing is something like a little regular expression that replaces the badges and images with empty strings in the readme's content (so the markdown can still function) good?
internal: { | ||
type: `NPMPackageReadme`, | ||
mediaType: `text/markdown`, | ||
content: hit.readme, |
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.
To fix the loadNodeContent
error — check that hit.readme is always defined as a string — so check if it's not defined and if it isn't, set it as any empty string.
…nditional rendering of specific metadata not pulled by every package
It's alive!!! https://deploy-preview-3906--gatsbyjs.netlify.com/packages/ :-D |
Yeah, we should be skipping any READMEs. The badges seemed affected by our default underline CSS for links — we could override that for these pages. |
soooo beautifulllll
…On Thu, Mar 1, 2018 at 5:01 PM, Kyle Mathews ***@***.***> wrote:
Yeah, we should be skipping any READMEs.
The badges seemed affected by our default underline CSS for links — we
could override that for these pages.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3906 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AEL3W8xiMCSmU4Pi8Dj8sHdiMi1pKBVIks5taJn4gaJpZM4R9oo8>
.
|
wow @gillkyle it looks awesomeeeeeeeeee. The search runs so fast I almost
thought it wasn't working lol! So speedy! Very excited!!!
On Thu, Mar 1, 2018 at 6:32 PM, Sam Bhagwat <notifications@github.com>
wrote:
… soooo beautifulllll
On Thu, Mar 1, 2018 at 5:01 PM, Kyle Mathews ***@***.***>
wrote:
> Yeah, we should be skipping any READMEs.
>
> The badges seemed affected by our default underline CSS for links — we
> could override that for these pages.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#3906 (comment)>,
or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/
AEL3W8xiMCSmU4Pi8Dj8sHdiMi1pKBVIks5taJn4gaJpZM4R9oo8>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3906 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Ae9o2uy9h8YJalSPtjNxruZQ4NP9Y4PFks5taKE8gaJpZM4R9oo8>
.
|
It doesn't seem to load all the examples? Eg https://deploy-preview-3906--gatsbyjs.netlify.com/packages?=source doesn't show 51 results, it shows only 20 or so. Should we be adding pagination? |
@calcsam yeah I had noticed that. I switched out the widget we were using for one that allows infinite scroll via a load more button (so it's basically paginated for every 20 results now). However, changing that added some issues to how the selected item in the search list works that I'm trying to sort out, fixing one thing just adds another issue 😅 |
Haha well almost there! The pagination looks nice. Let us know when the
selection issue is fixed and then we can merge in!
…On Sat, Mar 3, 2018 at 4:17 PM, gillkyle ***@***.***> wrote:
@calcsam <https://github.com/calcsam> yeah I had noticed that. I switched
out the widget we were using for one that allows infinite scroll via a load
more button (so it's basically paginated for every 20 results now).
However, changing that added some issues to how the selected item in the
search list works that I'm trying to sort out, fixing one thing just adds
another issue 😅
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3906 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AEL3W3hYJEhM2p8zxA76rUzQf1ZunNTsks5tazKsgaJpZM4R9oo8>
.
|
…ed, and added PropTypes and not found data so undefined errors don't break package readme template components
@calcsam @KyleAMathews I fixed the highlighting issue, I refactored how the pages for each package were created too because a few pages (I think it was 4) were getting skipped over and instead added in some default not found data. I think it's about there! 🤞 |
Cool! Merging. |
This is a continuation of #3456
A new dependency release and a few files (
www/gatsby_node.js
andyarn.lock
) caused issues with the Travis CI build. I forked the most recent branch from jastack and resolved those issues and removed thepackage-lock.json
file.There are still some things from the original thread (#3456 <-- that PR # is conveniently easy to type) that need to be resolved like some UI issues - mobile support, etc. - that I thought could be included later or summed up here and then worked on. I could also make a project board with all the remaining notes that need to be addressed if that would be helpful.
If there are other changes I should add before this moves forward I'd be happy to keep working on them!