These are chat archives for mirumee/saleor

18th
Aug 2018
Saqib khan
@saqibkhan2523
Aug 18 2018 01:09
@NyanKiyoshi Thanks alot man I will try to mplement it.
Filip Kucharczyk
@Pacu2
Aug 18 2018 11:03

Hi @stephenmoloney, we are planning to split the logic completely between the dashboard/frontend & backend. 
With, for example, storefront being completely separate repository. This way we could allow creation of several themes & frontends for saleor-based apps.

I think it will occur incrementally as it currently happens with the new dashboard, old version will be still supported for some time due to migration issues. It’s hard to give exact timeframe tho, might be in the next 2-3 months.

Data-wise I don’t think we have big plans when it comes to redesigning the current structure. Might be just a little clean up instead of turning everything upside down.

Stephen Moloney
@stephenmoloney
Aug 18 2018 11:05
@Pacu2 thanks for replying.

RE Hi @stephenmoloney, we are planning to split the logic completely between the dashboard/frontend & backend

That is good news. I think this is good because ideally I would like to have started with just the admin section and possibly create my own publically facing frontend and possibly backend logic myself.

But I need to start using it right away so I'll try with it as it is currently designed.
So @Pacu2, Another important consideration I din't see much documentation on is if you are moving to SPA, how are you going to handle authentication - oauth2 ?
It’s hard to give exact timeframe tho, might be in the next 2-3 months. Seems a little bit optimistic to me.
Stephen Moloney
@stephenmoloney
Aug 18 2018 11:10
Another thought I had was, rather than develop the new dashboard, storefront in branches in mirumee/saleor as it seems to be at the moment, why don't you start with new repos like saleor/dashboard, saleor/storefront, etc.... and leave mirumee/saleor alone as the unaffected legacy old version -- with support for some time to come.
I think developing on top of the old version makes things quite a bit more complex and introduces some risk.
Just some thoughts ... I really like what I've seen so far despite not being a python developer. But I'm not sure about the current model of integrating the graphql api incrementally on top of mirumee/saleor inside the mirumee/saleor repository.
Incremental development of the graphql app in new repositories saleor/microservice_a, saleor/microservice_b seems like a cleaner, lower risk approach. That way mirumee/saleor can become legacy and follow it's own tradional MVC path until it is no longer supported by anyone.