Extract theme module about krypt HOT 4 CLOSED

@mehdiyari, I thought that I added all compose dependencies to this module (Material3, Animation, Ui-tooling) so it's not limited to the theme
A better name would be more appropriate.
or considering that we ignore more separation for now and add ":core:designsystem" and add all related design stuff to it (shared drawable, strings, etc) and separate it in the future if needed

from krypt.

Hey @mhdabbaghy, Thanks.

The first thing that I want to tell you, based on our convention for modularization, is that we want to use something other than core or base names. We can have the design system modules in the design or shared directory.

:shared:designsystme:theme

from krypt.

@mehdiyari, I thought that I added all compose dependencies to this module (Material3, Animation, Ui-tooling) so it's not limited to the theme A better name would be more appropriate. or considering that we ignore more separation for now and add ":core:designsystem" and add all related design stuff to it (shared drawable, strings, etc) and separate it in the future if needed

Having this dependency inside the theme and providing dependencies as API to the rest of the modules is okay. Let's focus on getting the job done, and we can improve it in the future.

from krypt.

Hey @mhdabbaghy, Thanks.

The first thing that I want to tell you, based on our convention for modularization, is that we want to use something other than core or base names. We can have the design system modules in the design or shared directory.

:shared:designsystme:theme

Thanks @mehdiyari
I prefer design than shared,
But as you mentioned, let's get things done, i have no argue on that

from krypt.