Skip to content

Make it possible to have the State and the DecisionTable with the same name #163

@nergal-perm

Description

@nergal-perm

The idea is to have the state and behavior unified under the same name in the ComputationContext. Also that should make it possible to use something like this::property inside tables to get values from the associated state.

The reason for that is to have the ability to describe objects AND their behavior in the same table, not in a set of separate ones.

Probably the resulting tables will contain many irrelevant declarations though - I need to research that.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions