-
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
Topics/gatsby source medium | add limit #6200
Topics/gatsby source medium | add limit #6200
Conversation
Update the readme to explain use Minor format amend as there are now multiple options.
Deploy preview for using-drupal ready! Built with commit 9ab942c |
Deploy preview for gatsbygram ready! Built with commit 9ab942c |
Hey, I will open PR that fixes --edit: |
@seaburrows PR with fix I mentioned in previous comment was merged, so you can update your branch, which should fix |
@@ -1,5 +1,5 @@ | |||
{ | |||
"name": "gatsby-example-using-medmium", | |||
"name": "gatsby-example-using-medium", |
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.
🙈 😄
username: `smartive`, | ||
// username: `@ReactEurope`, | ||
// limit: 20, // note: the graphql query in src/pages/index.js also imposes a limit |
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.
commeting this one out is intentional?
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.
It was intentional yes. You can only have the one username but I wanted to show how to configure the limit in the example.
Do you think it should be the other way around?
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 would think that just documenting it in plugin docs would be enough, but we can keep it here
generally this is fine - just couple DX related suggestions:
|
ah okay sure, we can do those! So it would be:
|
Sounds great! |
@seaburrows -- would you be able to make changes discussed? we'd love to get this in! |
@pieh how do you feel about merging this in, then seeing if anyone wants to follow up with your suggested changes? |
Yeah, let's merge this in. |
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.
Thanks @seaburrows, we will merge that in as-is.
If anyone want to follow up with suggested DX changes, please open new PR for them :)
Holy buckets, @seaburrows — we just merged your PR to Gatsby! 💪💜 Gatsby is built by awesome people like you. Let us say “thanks” in two ways:
If there’s anything we can do to help, please don’t hesitate to reach out to us: tweet at @gatsbyjs and we’ll come a-runnin’. Thanks again! |
whoops, sorry for long silence. I've been super swamped. Glad this ended up getting in!! 🎉 😁 |
fixes #6181
Caveat
This isn't really tested 😱
There are no tests within this package and the
examples/using-medium
site is broken on master. After some digging around I can see that the netlify builds are failing with the same error I get: https://app.netlify.com/sites/using-medium/deploysSince the upgrade has been merged in (#5704) and the existing build is failing and I don't know how to fix them, I figured I'd open this PR rather than lose it.
Please let me know if I should be raising any other tickets.
Thanks!