microsoft / microsoft/RulesEngine
Feature: Rule Dependency Graph Visualization
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 4.4k
- Forks
- 616
- Avg merge
- 6m
- Merged PRs (30d)
- 2
Description
Feature: Rule Dependency Graphs (Visualization)
Objective:
Implement a feature that visualizes rule dependency graphs in the RulesEngine administration portal and/or API. This will help users understand how rules and workflows interconnect, making it easier to debug, optimize, and maintain complex rule sets.
Requirements:
- Analyze and extract rule dependencies from workflow definitions (e.g., rules referencing outputs of other rules).
- Generate a directed graph model representing these dependencies.
- Provide a backend API endpoint to retrieve dependency graphs for a given workflow version (e.g., as a JSON structure compatible with common graph libraries such as Cytoscape.js, D3.js, or Mermaid).
- (Frontend) Integrate a visualization component (e.g., D3.js, Cytoscape.js, or Mermaid) that consumes the backend graph and displays it interactively.
- Highlight potential issues: cycles, unreachable rules, or orphan rules.
- Optionally: Allow users to navigate from the graph to rule definitions for quick editing.
Acceptance Criteria:
- Backend exposes a dependency graph API for each workflow version.
- Admin UI displays the graph for any workflow.
- Cycles, orphans, and unreachable nodes are visually distinguished.
- Documentation updated for this feature.
References:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the workflow definitions and the RulesEngine Wiki to understand how rule outputs express dependencies. Review the administration portal and API entry points, then define the graph response and visualization approach. Done means each workflow version exposes a graph, the admin UI distinguishes cycles, orphan rules, and unreachable rules, and the documentation is updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend-api-design, documentation, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100