RnD/EVOLV
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases Wiki Activity

Externalize position constants to shared enum #3

New Issue
Closed
opened 2026-03-11 13:54:00 +00:00 by vps1_gitea_admin · 0 comments
vps1_gitea_admin commented 2026-03-11 13:54:00 +00:00
Owner
Copy Link

Problem

Strings "upstream", "downstream", "atEquipment" are hardcoded across 12+ files, with case sensitivity issues (atEquipment vs atequipment).

Current state

✅ POSITIONS constant created in generalFunctions/src/constants/positions.js
✅ Exported from generalFunctions/index.js

Remaining work

  • Gradually replace hardcoded strings with POSITIONS constants across all nodes
  • Add validation using isValidPosition() at config load time
  • Fix case sensitivity issues
## Problem Strings "upstream", "downstream", "atEquipment" are hardcoded across 12+ files, with case sensitivity issues (atEquipment vs atequipment). ## Current state ✅ POSITIONS constant created in generalFunctions/src/constants/positions.js ✅ Exported from generalFunctions/index.js ## Remaining work - [ ] Gradually replace hardcoded strings with POSITIONS constants across all nodes - [ ] Add validation using isValidPosition() at config load time - [ ] Fix case sensitivity issues
vps1_gitea_admin added the P0-architecture label 2026-03-11 13:54:00 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P0-architecture
Must-do structural/design changes for scaling
 P1-cleanup
Quick wins: remove deprecated code, fix inconsistencies
 P2-extensibility
Plugin architecture, output formats, config versioning
 P3-documentation
Docs, wiki, READMEs, architecture diagrams
 P4-testing
Test coverage, CI pipeline, integration tests
 bug
Confirmed bugs
 enhancement
New features / improvements
 security
Credentials, auth, vulnerabilities
 tech-debt
Code quality / cleanup
No Label P0-architecture
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
vps1_gitea_admin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: RnD/EVOLV#3
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?