# |
Oct 4th 2016, 18:06 |
Unfaiir |
easier migration sounds nice |
# |
Oct 4th 2016, 18:04 |
Unfaiir |
is this channel on slack? |
# |
Oct 4th 2016, 18:04 |
NeoThermic |
Well, there might be back ported 3.x features to make migration easier. |
# |
Oct 4th 2016, 18:04 |
Unfaiir |
perfect |
# |
Oct 4th 2016, 18:03 |
dakota |
There probably won't be any new features for 2.x, but bug fixes and security updates will still be done for a while |
# |
Oct 4th 2016, 18:01 |
dakota |
Thebreaker, yup |
# |
Oct 4th 2016, 18:00 |
Unfaiir |
slackebot1, sounds good, gives me time to migrate my clients to 3.x over time |
# |
Oct 4th 2016, 17:58 |
dakota |
which will not be any time soon |
# |
Oct 4th 2016, 17:58 |
dakota |
unfaiir, most likely until at least cakephp 4.0 is released |
# |
Oct 4th 2016, 17:54 |
NeoThermic |
Hopefully that puts the base64 PR closer to acceptance :) |
# |
Oct 4th 2016, 17:53 |
ndm |
@djbuss Result sets implement `ResultSetInterface`, which in turn extends `CollectionInterface` |
# |
Oct 4th 2016, 17:44 |
Unfaiir |
How long will development on CakePHP 2.x continue? |
# |
Oct 4th 2016, 17:34 |
djbuss |
is there any relation between Collection and the ORM resultsets ? |
# |
Oct 4th 2016, 17:04 |
inoas |
good evening bakress and bakers |
# |
Oct 4th 2016, 16:42 |
xymanek |
patsToms http://api.cakephp.org/3.3/class-Cake.Routing.RequestActionTrait.html |
# |
Oct 4th 2016, 16:37 |
patsToms |
"Check to see whether the request has a query param â??requestedâ?? with value 1." |
# |
Oct 4th 2016, 16:36 |
patsToms |
http://book.cakephp.org/3.0/en/controllers/request-response.html#Cake\Network\Request::addDetector |
# |
Oct 4th 2016, 16:36 |
patsToms |
what is the reason for request query param? |
# |
Oct 4th 2016, 16:33 |
NickBusey |
Hmm, doesn't look like there is an equivalent of 'bin/cake plugin assets symlink' for vendors, but it seems like there should be... |
# |
Oct 4th 2016, 16:11 |
inoas |
e.g. if someone is already using the hashkey model and scope (userland option) then stuff suddenly breaks |
# |
Oct 4th 2016, 16:10 |
inoas |
"If we are using B instead of A and userland code (custom PaginatorHelpers based on core PaginatonHelper) use 'scope' and 'model' and then call parent::, then the (here) updated Paginator will break, wouldn't it?" |
# |
Oct 4th 2016, 16:10 |
inoas |
dereuromark it is below @ https://github.com/cakephp/cakephp/pull/9564#discussion_r81680802 I think we should do as it is in my PR |
# |
Oct 4th 2016, 16:10 |
NickBusey |
what's the best practice for including assets from composer includes? I have files in vendor/fortawesome/font-awesome/fonts/ that I want in webroot/fonts/. Symlinking? Just moving them? Apache config? |
# |
Oct 4th 2016, 16:06 |
dereuromark |
ionas: what is your suggestion? |
# |
Oct 4th 2016, 16:05 |
Speud |
@djboz, because I have different role and dashboard ;) |
# |
Oct 4th 2016, 16:01 |
inoas |
dereuromark take a look at this comment possibly https://github.com/cakephp/cakephp/pull/9564#discussion_r81736209 |
# |
Oct 4th 2016, 15:58 |
ndm |
https://github.com/cakephp/cakephp/blob/master/src/ORM/Query.php#L568 |
# |
Oct 4th 2016, 15:58 |
ndm |
Under the hood, `innerJoinWith` calls the same routine as `matching` does, but with an additional `'fields' => false` option, doing a select in the builder properly wins over the option. |
# |
Oct 4th 2016, 15:56 |
birdy247 |
Cheers ionas |
# |
Oct 4th 2016, 15:55 |
birdy247 |
:slightly_smiling_face: |
# |
Oct 4th 2016, 15:54 |
inoas |
I'd suggest to use matching where you want to actually return data and innerJoinWith where you dont want to ;) or so |
# |
Oct 4th 2016, 15:53 |
inoas |
birdy247 innerJoinWith + select() => _matchingData? |
# |
Oct 4th 2016, 15:45 |
birdy247 |
you can make it mimic matching if you sue the select option |
# |
Oct 4th 2016, 15:45 |
birdy247 |
ahhh neat |
# |
Oct 4th 2016, 15:44 |
birdy247 |
I thought this would not happen with innerJoinWith |
# |
Oct 4th 2016, 15:43 |
birdy247 |
but getting a _matchingData in my returned results |
# |
Oct 4th 2016, 15:43 |
birdy247 |
I am using innerJoinWith |
# |
Oct 4th 2016, 15:41 |
djboz |
false* |
# |
Oct 4th 2016, 15:41 |
djboz |
So, why use prefix = aflse? |
# |
Oct 4th 2016, 15:40 |
Speud |
from the official doc:: The scope and contain options have been deprecated as of 3.1. Use a custom finder instead to modify the query to fetch a user record |
# |
Oct 4th 2016, 15:39 |
Speud |
I read in the doc in 3.3.5, contain in deprecated in Auth, you have to know use a custom finder if you want to use it (but still working with contain at this time) |