Editor.add_member() has no kind for perform-action usages
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- go
- Domain
- backend-api-design
Research direction
Start at the Editor.add_member() entry point and inspect its allowed member-kind handling, then compare it with the load_from_content path for a perform action usage. Add coverage for kind="perform action" so editor.apply() accepts the construct consistently with SysML text loading.
Written by the indexing model from the issue text.
Description
Summary
Editor.add_member() has no kind for a perform-action usage. apply() raises IllegalMemberKindError for kind="perform action", even though the equivalent construct loads fine as SysML text.
Version: OpenSysML v0.9.0.
Observed
editor = model.edit()
editor.add_member(owner="P::H", kind="perform action", name="heat", ...)
editor.apply()
# IllegalMemberKindError: kind "perform action" is not legal in SysML source
perform action heat : ToastBread; inside a part def loads without issue when supplied as SysML text via load_from_content.
Reference
SysML v2.0 (formal/2026-03-02), 7.17.6 Perform Action Usages — the construct that records which logical component is responsible for performing a given action.
Request
Add perform action to the Editor.add_member() allowlist, alongside the existing coverage requests for allocate (#599), flow, and state usages — this repo hits all of them in the same authoring pattern (a logical component performing a function).
- Dominant language
- Go
- Stars
- 24
- Forks
- 5
- Avg merge
- 10h 1m
- Merged PRs (30d)
- 512
Getting set up
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.
More from Open-MBEE/OpenSysML
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
All issues in Open-MBEE/OpenSysML
Similar issues
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
netdata/netdata#24062 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
meshery/meshery#22119 · 1 comment ·
Maintainers usually reply within 1 day
-
automation documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day