What are the Slack Archives?
Itβs a history of our time together in the Slack Community! Thereβs a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you wonβt be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
π there are Abstract Plugins for the `Client`, `Service`, `Glue`, `Yves` and `Zed\Kernel\Commu
π there are Abstract Plugins for the Client
, Service
, Glue
, Yves
and Zed\Kernel\Communication
. Is there an extension point for Zed\Business
?
Comments
-
the plugins in the communication layer should access the business logic through the facade
0 -
so, there should be no plugin in the business layer
0 -
but maybe i donβt get the question
0 -
so I guess my question is what if the plugins do not concern the communication layer?
0 -
or is it implicit that anything that "communicates" with the module should be there?
0 -
si
0 -
can you elaborate on your scenario?
0 -
I'm creating a "debug" module, which will collect information about some stuff (entities) and render reports.
the reports are plugins
0 -
then the above β
0 -
communication/plugin -> business/facade
0 -
coool
0 -
and if you wanted to bundle a bunch of "plugins" in a module which were for other modules?
0 -
would there be a precedent for that? (don't necessarily want to create a dozen bridge modules)
0 -
if that makes sense
0 -
π€
0 -
donβt really get your idea then
0 -
sounds like a white-board-moment
0 -
so we create a module: https://github.com/inviqa/spryker-debug
0 -
and would like to have (as a new feature) "report" plugins for various entities from various other spryker modules
0 -
so one "clean" way would be to have a "bridge" for each plugin, but reluctant to add that degree of complication
0 -
(might make more sense in a whole new package then probably)
0 -
Hey Dan, for plugins you donβt need bridge, you can define plugin interface in separate module, e.g. SprykerDebugExtension
0 -
So other spryker modules will require this module and implements your interface
0 -
hey, I'm talking about implementations here
0 -
e.g. we want a report plugins for products, availability, URLs, etc
0 -
so technically I guess each would need a bridge module ?
0 -
we would call it connector module, but that sounds about right
0 -
but i would actually still prefer to discuss that in person, to better understand the plan
0 -
sure can do
0 -
(note that it's an open source thing I'm doing between projects)
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 73 Spryker News
- 911 Developer Corner
- 771 Spryker Development
- 87 Spryker Dev Environment
- 361 Spryker Releases
- 3 Oryx frontend framework
- 34 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 25 Job Opportunities
- 3.2K π Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 69 Spryker Safari Questions
- 50 Random