The module development and code questions forum is intended to aid those who are developing modules or writing code for Drupal.
Please note that this forum is also not intended for "Is there a module that does..." or "I need help with module x..." questions. It's also not a place to ask developers to write your code for you. Please respect this.
Please do not post general discussions intended to target module developers. If the question you have isn't specifically related to writing a drupal module, please post it in a more appropriate forum.
If you you have drupal installed already and are seeking a module that does a specific task, have a question about a specific module and what it does or if it will fit your use case, please place your questions in the Post installation forum.
If you have a problem or question about a specific module, you should create an issue in the module's issue queue (after checking for an existing issue first).
If you don't have drupal installed yet, please place your questions in the Before you start forum.
Let's look two modules: voting_api and dblog from core. Voting_api uses entity for storage and manage votes. In other words each vote is entity. Dblog module does query in db and each log message simple row in db table. But each log message possible considered as entity. Why ? How do I determine when use entity ?
I need to be able to run code that does not output any data to the user after a user's checkout is complete, but I can't seem to figure out how Commerce wants me to do it. I don't see any *.api.php files that would give me payment hooks. It looks like Commerce wants me to create a separate Checkout Flow plugin that would add the step I want, but I can't seem to find documentation about implementing my own Checkout Flow.
Can you guide me to the right path of running my code when the checkout is complete? Am I on the right path? Can you point to Checkout Flow development docs?