-
Notifications
You must be signed in to change notification settings - Fork 197
Add DCFor in pathfinding filter #1653
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
WalkthroughA new edge type, Changes
Suggested labels
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🧰 Additional context used🧠 Learnings (2)📓 Common learnings
packages/javascript/bh-shared-ui/src/edgeTypes.tsx (1)
⏰ Context from checks skipped due to timeout of 90000ms (4)
🔇 Additional comments (1)
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Description
Add DCFor edge in pathfinding filter menu
Motivation and Context
Resolves BED-5968
The edge is traversable, so it should be in the path finding filter.
How Has This Been Tested?
Tested by running code locally.
Upload this dataset:
20250414000418_BloodHound.zip
Go to the Explore page and to pathfinding. Verify DCFor appears under AD structure data.
Screenshots (optional):
Types of changes
Checklist:
Summary by CodeRabbit