SethFalco/commandler
SethFalco/commandler
Watch
1
Code Issues 44 Pull requests Projects Releases Packages Activity Actions

Allow Events to Manipulate Controller/Command Properties #49

New issue
Open
opened 2019-07-20 01:03:24 +01:00 by Ghost · 0 comments
Ghost commented 2019-07-20 01:03:24 +01:00 (Migrated from codeberg.org)
Copy link

Feature Request

Sub-Project

  • core

Description

Events should be able to override certain properties of Commandler somehow.
For example, the StandardDispatcher has a isStatic configuration. A certain event may want to mark a module as isStatic for that event only.

Motivation

This allows Commandler to be more finely configured on a per event level rather just a static global configuration.

We will have to keep an eye on validation for this though as this can also cause problems.

Interface

# Feature Request <!-- If you feel a heading is irrelevant, just leave it empty or remove it. --> ## Sub-Project <!-- Can you specify which sub-project(s) this is relevant to? If you aren't sure, or this is a proposal for a new sub-project, you can delete this. --> * core ## Description <!-- Explain what this is about, try to use full sentences, and make your point clear. --> Events should be able to override certain properties of Commandler somehow. For example, the `StandardDispatcher` has a `isStatic` configuration. A certain event may want to mark a module as `isStatic` for that event only. ## Motivation <!-- Why is this a feature that should be implemented in Commandler rather than in your own project using it? What makes this fundamental, or reusable, or of demand to other developers? --> This allows Commandler to be more finely configured on a per event level rather just a static global configuration. We will have to keep an eye on validation for this though as this can also cause problems. ## Interface <!-- In some cases you may wish to propose an interface or method names to help describe how you'd want to use this, or for others to discuss and improve ahead of time before final implementation. -->
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
i18n
4.0.1
Labels
Clear labels   
bug
Something that's not working as intended in an existing project's functionality.

  
feature-request
A brand new feature for an existing project.

  
upstream
Should be resolved through an upstream contribution.

No labels
bug
feature-request
upstream
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
SethFalco/commandler#49
No description provided.