gatsbyjs/api.gatsbyjs.org

The API for the Gatsby swag store.

api.gatsbyjs.org's Issues

Instructions on how to start the project locally is out of date

• Clone url is out of date/invalid
• Might be worthwhile explaining the environment variables needed

https://github.com/gatsbyjs/api.gatsbyjs.org/blob/f2d7f845b162ed5f9d75bc7d5f1c99c31f56bb39/README.md#step-1-start-the-api-locally

Improve CORS handling (again)

See https://github.com/serverless/forms-service/blob/master/backend/serverless.yml#L98-L117

Via https://twitter.com/DavidWells/status/1075434951242215424?s=19

tier 2 swag: [implement/api] Modify API to check for second tier contributions

In order to qualify for tier 2, contributors need to have made five or more contributions (currently measured as PRs -- so 5+ PRs)

On login, we already check number of contributions. Need to add additional logic for tier 2.

Convert get() function to use querystring and accept an object

Right now the get() helper requires passing in a query string, e.g. foo=bar&bat=baz.

It would be better if we could pass in an object, e.g.:

get(uri, { foo: 'bar', bat: 'baz' })

This would be converted to a query string (could use a lib such as querystring), which makes it a little easier to use this helper.

Don’t add to MailChimp if the option is set to false

The /store/discount-code endpoint receives a subscribe parameter.

• Add the subscribe parameter to the docs
• Check the subscribe parameter and only call MailChimp if it’s set to true

Free swag codes can be used multiple times

As I was discovering the bug resolved in #7, I noticed that I was able to apply the promo code again to get free swag. I didn't fully complete the checkout, so I don't know if there would have been an error, but I would have expected Shopify to have warned about an invalid code.

A bit of research revealed shopify has a once_per_customer option for their PriceRules. I wanted to point this out incase you don't have it set.

[SUB-EPIC] Contributor Levels + Discount Code Use Tracking

NOTE: This issue is an epic, which bundles up lots of related issues into a single goal. If you have the free ZenHub extension, you’ll be able to see overall progress and related issues, as well as a "board view" that shows this epic from a bird's-eye view.

This is a sub-epic of gatsbyjs/store.gatsbyjs.org#168

Who will own this?

Area of Responsibility: Ecosystem

Role	Name	RACI
AoR owner	@amberleyromo	Consulted about the epic
Domain owner	@amberleyromo	Informed about epic
Project manager	@jlengstorf	Responsible for setting epic tasks
Tech lead	@amberleyromo	Accountable for setting guidelines for epic
Contributors	@amberleyromo @jlengstorf	Responsible for completing assigned tasks

Summary

Extend the Gatsby store API to support multiple levels of contributor rewards, as well as keeping track of whether or not a contributor has used a given discount code.

How will this impact Gatsby?

Domains

• Gatsby store

Goals

1. Add support for returning multiple discount codes for differing levels of contribution
2. Add a flag for whether or not the discount code was already used by the contributor

How will we know this epic is a success?

We know this is a success when the API returns sufficient data to complete the parent epic.

Cold start on Lambda seems to trigger CORS errors

We have intermittent CORS failures, and the flow seems to be something like this:

1. Visit the store
2. Log in
3. The "open issues" section errors out with CORS errors
4. Reload the page
5. No CORS error; open issues load just fine

I have no proof, but my suspicion is that this is an issue with AWS Lambda "cold starts". I'm not sure if there's a for-real fix, but the smash-it-with-a-hammer fix is to keep the lamda warm.

Looks like Serverless has a plugin for this (see this tutorial), so we just need to put this in place.

Switch to GitHub’s GraphQL API

See https://github.com/octokit/graphql.js — need to check if the GraphQL API supports all the things we need, though.

tier 2 swag: [implement/api] add a check for whether or not a coupon code has been redeemed

(ported from @jlengstorf comment: https://github.com/gatsbyjs/store.gatsbyjs.org/issues/170#issuecomment-435932868)

I think the way this will work is:

• Load all orders for the given customer
• Check if any discount codes were used
• Match those discount codes against our contributor level discount codes
• Return a status for each code.

Relates to #170

tier 2 swag: [implement/api] return appropriate coupon codes to user on login

• if a user has met the criteria for tier 1, return tier 1 coupon code.
• if a user has met the criteria for tier 2, and redeemed tier 1 but not tier 2, return a tier 2 coupon code.
• if a user has met the criteria for tier 2, and redeemed neither tier 1 nor tier 2, return a tier 1 and a tier 2 coupon (two coupons)
• if a user has met the criteria for both tiers, and claimed both coupon codes

Add an endpoint for anonymous data reporting

cc @DSchau

We need a way to send anonymous usage data from the Gatsby CLI. This will require creating an endpoint in the API that accepts a data object (such as the envinfo and other data about a Gatsby site that helps us debug) and stores it somewhere secure.

Potentially, this will allow us to create public data visualizations (via new queries that will expose various stats about Gatsby usage). We'll have to think more about whether there are any risks to making usage data publicly queryable, but it would be really cool to be able to see how Gatsby is growing, what plugins/starters are popular, etc.