Calling Developers!
We are reenergizing our code contribution process! Learn More

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..

Hi there, is there a concept in spryker how to “reuse” code within several modules? Maybe a link to

Options
U03FNK5A87J
U03FNK5A87J Posts: 26 🧑🏻‍🚀 - Cadet

Hi there, is there a concept in spryker how to “reuse” code within several modules? Maybe a link to a documentation.

Comments

  • See services, like e.g. Util services.

  • U03FNK5A87J
    U03FNK5A87J Posts: 26 🧑🏻‍🚀 - Cadet
    Options

    Quote:

    “A service is a Spryker application layer shared by the Client, Zed, and Yves application layers”

    https://docs.spryker.com/docs/scos/dev/back-end-development/messages-and-errors/registering-a-new-service.html#how-to-use-a-service

    Does not seems to be a way to reuse code within severals modules.

  • Unknown
    edited February 2023
    Options

    In this case I am not referring to them regarding layer.
    Sure, they can be "used" from almost every layer.
    But the main point here is that those can also be used across modules as reusable part (see e.g. composer json encoding/decoding for 10+ modules).

    Maybe I used the wrong word. "Util" modules sounds better.
    So a module that has a facade entry that then internally might very well use a servive or other elements.

    That said:
    This only is relevant for (vendor level) module dev.
    If you develop on project level, you can also directly put classes inside others to be used.
    Especially if they provide static methods or other stateless approaches.

    As you are on the top level of dependency tree and in full control of your dependencies, and not possible to create cyclic composer dependencies through this.