Hi, thanks for your tutorial, I do have a few questions. I scaffolded an app with React Remix template 1. You said you are going to add the mutation once the app is installed, i really need to know, where do you do that? 2. I noticed that I had to delete the webPixel and re-add again to have it have my updated webPixel code. What if 10k users install my app and I decide to update the code of a webpixel? What is the industry standard for this?
Seriously, you didn't provide the code used in the tutorial? Do you expect us to input it manually? What if the tutorial is outdated or the Gadget has been updated? I'm speechless - spending so much time only to find out it doesn't work.
This is a tricky one! There isn't really a great out-of-the-box, automated solution for this right now. Some developers have built custom scripts that do string matching and replacement based on a passed in variable (which is usually the environment). And then this script can be run during a CI/CD pipeline when deploying to production (or when changing/starting up development environments) to make sure that the extension is always targeting the correct Gadget environment Providing a better fix for this is on our todo list!
Hi, thanks for your tutorial, I do have a few questions. I scaffolded an app with React Remix template
1. You said you are going to add the mutation once the app is installed, i really need to know, where do you do that?
2. I noticed that I had to delete the webPixel and re-add again to have it have my updated webPixel code. What if 10k users install my app and I decide to update the code of a webpixel? What is the industry standard for this?
The webpixel is not working instantly in browser because shopify always cache their websites, and do don't have live webpage rather some old version
Seriously, you didn't provide the code used in the tutorial? Do you expect us to input it manually? What if the tutorial is outdated or the Gadget has been updated? I'm speechless - spending so much time only to find out it doesn't work.
What's the best way to manage sending to development and production routes? (instead of hard coding like the example)
This is a tricky one! There isn't really a great out-of-the-box, automated solution for this right now.
Some developers have built custom scripts that do string matching and replacement based on a passed in variable (which is usually the environment). And then this script can be run during a CI/CD pipeline when deploying to production (or when changing/starting up development environments) to make sure that the extension is always targeting the correct Gadget environment
Providing a better fix for this is on our todo list!