| # |
Aug 22nd 2019, 19:31 |
 ndm |
Actually, `Console.buildCommands` was a different problem... don't remember exactly |
| # |
Aug 22nd 2019, 19:30 |
ndm |
Depending on what the plugin does you might be able to leverage existing events... and now I somewhat remember what the problem was about, I needed the config before the middleware is being built, and there was no other event before `Server.buildMiddleware`/`Console.buildCommands`, which both happens after the middleware is built. |
| # |
Aug 22nd 2019, 19:25 |
generitter |
@ndm Thanks that’s not a bad idea. Wish there was a way to do it on a framework event. |
| # |
Aug 22nd 2019, 19:24 |
slackebot2 |
Configure::write('Plugin.config', 'value'); }); ``` There was another way which I discarded because it wouldn't work properly, but I don't really remember what that was about... |
| # |
Aug 22nd 2019, 19:24 |
ndm |
@generitter I remember using events in the test application class for that, like: ``` class Application extends BaseApplication { public function pluginBootstrap() { parent::pluginBootstrap(); EventManager::instance()->dispatch(new Event('TestApp.afterPluginBootstrap')); } // ... } ``` And then in the test case: ``` EventManager::instance()->on('TestApp.afterPluginBootstrap', function () { |
| # |
Aug 22nd 2019, 19:02 |
generitter |
When doing integration testing, does anyone know how to change the application/plugin configuration values? Configure::write() doesn’t work when running plugin controller integration tests from the outer application. |
| # |
Aug 22nd 2019, 17:15 |
nemmons |
@abhilashlohar i created a src/functions.php file for a few global functions. i load it in composer.json like... ``` "autoload": { "psr-4": { ... }, "files": [ "src/functions.php" ] }, ``` |
| # |
Aug 22nd 2019, 16:43 |
abhilashlohar |
In CakePHP 3.x, I want to create a global function which will be utilized throughout the application. How should I achieve? Thanks in advance |
| # |
Aug 22nd 2019, 16:41 |
abhilashlohar |
Good day to everyone |
| # |
Aug 22nd 2019, 15:31 |
alexdd55976 |
now you got me all confused :) |
| # |
Aug 22nd 2019, 15:31 |
ricksaccous |
makes sense |
| # |
Aug 22nd 2019, 15:31 |
nemmons |
(well, i am also trying to avoid using the old AuthorizationComponent for the same reason) |
| # |
Aug 22nd 2019, 15:30 |
nemmons |
ah yeah sorry, i should have specified |
| # |
Aug 22nd 2019, 15:30 |
ricksaccous |
which is the new stuff |
| # |
Aug 22nd 2019, 15:30 |
ricksaccous |
no he's talking about the authorization component that comes with the plugin |
| # |
Aug 22nd 2019, 15:30 |
alexdd55976 |
it will be deprecated in the near future, won't it? |
| # |
Aug 22nd 2019, 15:30 |
nemmons |
that way i can just unit test the policies and not worry about devs doing weird shit in controllers to break the auth |
| # |
Aug 22nd 2019, 15:30 |
ricksaccous |
i see |
| # |
Aug 22nd 2019, 15:29 |
nemmons |
i'm trying to avoid using the AuthorizationComponent at all because it seems to make more sense to do all the Auth at the middleware level |
| # |
Aug 22nd 2019, 15:29 |
nemmons |
nah i think you're right. i was hoping this would automagically apply model-based policies using the OrmResolver |
| # |
Aug 22nd 2019, 15:29 |
ricksaccous |
also with requestAuthorizationMiddleware do not expect to be able to use the component |
| # |
Aug 22nd 2019, 15:28 |
ricksaccous |
i was hoping i could do those things when i set it up. lol |
| # |
Aug 22nd 2019, 15:28 |
ricksaccous |
maybe i'm not making any sense/am wrong |
| # |
Aug 22nd 2019, 15:28 |
ricksaccous |
i dunno |
| # |
Aug 22nd 2019, 15:27 |
ricksaccous |
but you can still map policy resolvers on top |
| # |
Aug 22nd 2019, 15:27 |
ricksaccous |
policy resolvers |
| # |
Aug 22nd 2019, 15:27 |
ricksaccous |
so i think you won't have the automagic of the uhhh |
| # |
Aug 22nd 2019, 15:27 |
ricksaccous |
but yeah, i'm wrong |
| # |
Aug 22nd 2019, 15:27 |
nemmons |
ugh |
| # |
Aug 22nd 2019, 15:27 |
ricksaccous |
you'll have their identity at that stage |
| # |
Aug 22nd 2019, 15:26 |
ricksaccous |
yeah so you pretty much read the request and authorize them based on what you read |
| # |
Aug 22nd 2019, 15:26 |
ricksaccous |
now that i'm looking at it |
| # |
Aug 22nd 2019, 15:26 |
ricksaccous |
but yeah i did use map resolver |
| # |
Aug 22nd 2019, 15:26 |
ricksaccous |
it's been a while |
| # |
Aug 22nd 2019, 15:25 |
ricksaccous |
you're probably right |
| # |
Aug 22nd 2019, 15:25 |
ricksaccous |
sorry |
| # |
Aug 22nd 2019, 15:25 |
ricksaccous |
actually |
| # |
Aug 22nd 2019, 15:25 |
nemmons |
I must be horribly misreading https://book.cakephp.org/authorization/1.1/en/request-authorization-middleware.html#using-it then |
| # |
Aug 22nd 2019, 15:25 |
ricksaccous |
@nemmons no that's not really how RequestAuthorization middleware works |
| # |
Aug 22nd 2019, 15:24 |
alexdd55976 |
i added it to my new cake4 project, but no idea how it works. seems not very approachable |
| # |
Aug 22nd 2019, 15:24 |
nemmons |
ah, perhaps you're forced to use the MapResolver rather than the other policyresolvers and then you map the request to the resource or something like that... as kind of hinted of in the documentation? |