vscode extension view with expose and filter condition shows nothing
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
The payload names no files, so start by reproducing the fails view from the issue text with the sysml-lsp language server and the CLI, and compare what each renders. Find where the filter @PartUsage condition is applied to the exposed elements in the InterconnectionView path. Read the five comments first, since they may already narrow the cause. Done means the fails view renders the same diagram as the works view, filtered to part usages, with a regression test.
Written by the indexing model from the issue text.
Description
What happened, and what you expected instead
When I use VS code extension on example below, I get no diagram for interconnection view that uses filter condition.
Command line tools for getting diargams work fine.
Reproduction
package Model {
part abcd {
part a {
port a;
}
part b {
port b;
}
action d;
interface i connect (a.a, b.b);
part c;
port p;
}
private import StandardViewDefinitions::*;
view fails: InterconnectionView {
expose abcd;
filter @PartUsage;
}
view works: InterconnectionView {
expose abcd;
}
}
Version
0.10.0-nightly-20261015-6b8187298
Surface
Language server (sysml-lsp) / VS Code extension
Platform
Ubuntu 24
- Dominant language
- Go
- Stars
- 39
- Forks
- 12
- Avg merge
- 14h 14m
- Merged PRs (30d)
- 759
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from Open-MBEE/OpenSysML
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 15/100
Open-MBEE/OpenSysML#1212 · 1 reaction ·
Maintainers usually reply within 1 day
-
bug spec compliance
Difficulty 4/5 3-5 days Newbie friendliness 18/100
Open-MBEE/OpenSysML#1125 · 3 comments ·
Maintainers usually reply within 1 day
-
help wanted question
Difficulty 5/5 Over a week Newbie friendliness 25/100
Open-MBEE/OpenSysML#987 · 11 comments ·
Maintainers usually reply within 1 day
All issues in Open-MBEE/OpenSysML
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
keyxmakerx/Chronicle#1469 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Gentleman-Programming/gentle-ai#5565 · 1 comment ·
Maintainers usually reply within 1 day
-
bug frontend grammar sev-3
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
-
connector docs good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
soma-intelligence/open-health-sync#134 ·
Maintainers usually reply within 1 day
-
bug frontend
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 3 days