TEN-framework / TEN-framework/ten-framework
feature request: add type alias support for env placeholder
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11.1k
- Forks
- 1.4k
- Avg merge
- 2d 15m
- Merged PRs (30d)
- 22
Description
Currently ${env:xxx} supports env text only. Now we need to support more types such as int64 for more import flexibility. For example, when an agent master tries to launch an new agent service, some parameters can be imported for the launching.
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 locating the implementation and tests for the ${env:xxx} placeholder, then trace how launch parameters are parsed for agent services. Clarify the supported type aliases and expected conversion behavior, including int64; done means the requested typed imports work without breaking existing environment text handling and are covered by tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100