You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I see we have a separate Yii app shopify with its own config. Why do we need this? Also, we have some tables and models (shopify_app, shopify_webhook) but in my case they are empty. Why do we need this?
This can be deleted and removed. It was going to be used for a Shopify App but was never fully tested or finished.
Shall I continue using the existing page /integration and existing code+tables? I mean, as the basis.
Am I allowed to edit the current logic? For instance, you'd like to add the "Pause" state. Also, I'd probably upgrade something here )
Yes. It is not used in production feel free to change all.
Am I right that I need to add the ability to connect/disconnect a service using OAuth on the /integrarion page? For the moment, you'd like to have the ability to connect/disconnect Shopify on the page /integration?
Yes
If leave the page /integration available only for the admin, then using OAuth he would be able to authorize only himself. I'm not sure it's correct. Can you please clarify this moment? I have an assumption that we should have a new Integrations page available for all users where they will be able to connect their Shopify using OAuth. Or shall I keep using the form below (attached image) where we connect a customer with an integration?
The /integration page will be available for all customers/users after testing.
If we leave the current page /integration and upgrade it (add Shopify, add the ability to pause an integration, add the ability to use OAuth, etc.), then here, in the form, we keep linking customers with integrations, correct?
Feel free to redesign the flow or add any forms. This will mainly be customer facing for them to connect ecommerce sites.
feel free to create other issues if you feel like we need to separate some of the code out.
Since /integration isn't used, maybe I'd separate a task with Integrations (like a basic functionality with tables, models, forms, etc.) itself and then Shopify integration as a separate task extended from Integrations (basic logic).
@cgsmith I implemented some basic logic for E-commerce Platforms and Integrations. Please have a look when you have time - #155
Just to be sure I understood you correctly) If you have any corrections, let me know.
Maybe we should not merge the PR right now since I'm going to implement adding Shopify extended from the branch. In this branch, I added Shopify only as a mock E-commerce Platfom. In addition, it has only initial logic without "real needs".
This can be deleted and removed. It was going to be used for a Shopify App but was never fully tested or finished.
Yes. It is not used in production feel free to change all.
Yes
The /integration page will be available for all customers/users after testing.
Feel free to redesign the flow or add any forms. This will mainly be customer facing for them to connect ecommerce sites.
feel free to create other issues if you feel like we need to separate some of the code out.
It's related to #137
The text was updated successfully, but these errors were encountered: