core requirements

27 views
Skip to first unread message

IamPersistent

unread,
Oct 6, 2013, 5:09:55 PM10/6/13
to vespol...@googlegroups.com
Right now, core has hard dependencies on 


Should this be necessary? I'm in a situation where I am using the library for tracking payment transactions only. I don't need any of the hard dependencies. It seems to me that I shouldn't be required to include them when I do not need them.

Unless there is a compelling reason to require them, I'm going to move them to dev and suggested.

Daniel Kucharski

unread,
Oct 7, 2013, 1:34:02 AM10/7/13
to vespol...@googlegroups.com
I am fine making then optional and having the developer to explicitly indicate which additional dependencies he will be needing.  In a V context it means that you will need to move these dependencies to v/commerce or v/commerce-bundle

6 Oct 2013 23:09
--
You received this message because you are subscribed to the Google Groups "vespolina-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vespolina-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--

Xerias
 
Daniel Kucharski
Reepstraat 56,
9185 Wachtebeke
Mobile: +32 (0)479 85 47 39
 
 

Willem-Jan Zijderveld

unread,
Oct 7, 2013, 1:45:54 AM10/7/13
to vespol...@googlegroups.com, vespol...@googlegroups.com
Looks like a good idea. I would like to see as little dependencies as possible per library/bundle. 
Where possible, it would be great to only add the depencies you absolutely can't live without and make other libraries optional by code and add those to suggest. 
For example, if we would use sonata for an admin later, it would be nice to add a check in the Extension if it's installed and only then enable our functionality for it. 


On Mon, Oct 7, 2013 at 7:34 AM, Daniel Kucharski <dan...@xerias.be> wrote:

I am fine making then optional and having the developer to explicitly indicate which additional dependencies he will be needing.  In a V context it means that you will need to move these dependencies to v/commerce or v/commerce-bundle

<compose-unknown-contact.jpg>
6 Oct 2013 23:09
Right now, core has hard dependencies on 


Should this be necessary? I'm in a situation where I am using the library for tracking payment transactions only. I don't need any of the hard dependencies. It seems to me that I shouldn't be required to include them when I do not need them.

Unless there is a compelling reason to require them, I'm going to move them to dev and suggested.
--
You received this message because you are subscribed to the Google Groups "vespolina-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vespolina-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Luis Cordova

unread,
Oct 7, 2013, 8:21:16 AM10/7/13
to vespol...@googlegroups.com
I am all for decoupling, dependencies should be inverted totally

Daniel Kucharski

unread,
Oct 7, 2013, 5:15:12 PM10/7/13
to vespol...@googlegroups.com
Ok, i've moved the dependencies to suggest.

7 Oct 2013 14:21
I am all for decoupling, dependencies should be inverted totally



--
You received this message because you are subscribed to the Google Groups "vespolina-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vespolina-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
7 Oct 2013 07:45
Looks like a good idea. I would like to see as little dependencies as possible per library/bundle. 
Where possible, it would be great to only add the depencies you absolutely can't live without and make other libraries optional by code and add those to suggest. 
For example, if we would use sonata for an admin later, it would be nice to add a check in the Extension if it's installed and only then enable our functionality for it. 



--
You received this message because you are subscribed to the Google Groups "vespolina-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vespolina-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
7 Oct 2013 07:34
I am fine making then optional and having the developer to explicitly indicate which additional dependencies he will be needing.  In a V context it means that you will need to move these dependencies to v/commerce or v/commerce-bundle


--
You received this message because you are subscribed to the Google Groups "vespolina-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vespolina-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Reply all
Reply to author
Forward
0 new messages