Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
dream dream
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • nexedi
  • dreamdream
  • Issues
  • #1

Closed
Open
Created Feb 01, 2016 by Ghost User@ghost

Overview question: What's the order of methods that are called in a core object?

Say I want to execute some code at just after a machine receives an entity, but before any internal machine processing has taken place? Similarly, how would I run some code after the machine has completed and just before hand-off to another object?

Is there a quick function rundown or diagram that easily shows what happens (and at what times) within each machine so I know where best to attach custom code to operate on entities passing through the system?

Here's a high level of how I'd see it working: high_level_machine

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7