NASA-AMMOS / NASA-AMMOS/plandev
Remove Profile Wrapping from Activity Parameters
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 128
- Forks
- 33
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
Currently, Activity Parameters are wrapped in Profiles with a single segment. This means that in constraints it is impossible to directly access the value.
Example use case: Activity Type A has a max_duration parameter. It would be useful to use this parameter in a shiftBy statement.
Backwards compatibility concern: We currently support filtering Windows examined in a Constraint based on comparisons to Activity Parameters.
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
The issue names no files, tests, or entry points. Start by tracing how Activity Parameters are wrapped in single-segment Profiles and how constraints compare them, then define behavior for direct parameter access while preserving existing Window filtering. Done when the parameter can be used directly in a shiftBy statement and compatibility behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100