Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Why write an article for a broken code base?

See original GitHub issue

I did not feel any of the questions were relevant to my “issue” I’m just curious as to why This article on Medium is NO WHERE near accurate to: nextjs-react-strapi-deliveroo-clone-tutorial ?

These sorts of things just throw people off as I’m sure you can tell by all the comments. Being that this is an “official” strapi article, it only makes sense that you properly write the article and don’t leave steps out that appear to be sending everyone for a loop.

Issue Analytics

State:
Created 4 years ago
Reactions:7
Comments:5 (1 by maintainers)

Top GitHub Comments

2reactions

krynvcommented, Nov 7, 2019

Have these been rewritten & submitted anywhere yet?

1reaction

Palgiecommented, Sep 6, 2019

@soupette Thanks for revisiting these articles. If I could I’d like to put these two ideas forward for the refresh:

Back-end validation of the payment from Stripe (as @Pedrock mentioned).
Syncing product records to Stripe to use alongside Stripe Orders API rather than simple Stripe Transactions (Maybe a good way to demonstrate using Strapi lifecycle updates to mirror create / update)

Think these would make a great difference to the end result due to the added benefits.

Excited to see the see the new articles and source!