Be less stringent for port names in actions & triggers
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 126
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
It seems I'm often running out of good names for ports. We should relax the name collision rules
Contributor guide
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 locating the port-name collision validation for actions and triggers, then trace how names are checked during compilation. Clarify which collisions should remain errors and which names should be accepted; done means valid port names are no longer rejected while genuine collisions still are.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100