Make code_aster input file writing faster, safer, and more accessible directly from VS Code.
The extension aims to reduce friction between modeling, validation, execution, and analysis by bringing code_aster native workflows into the editor.
.exportfile generator- 3D mesh viewer
- code_aster command language auto-completion with inline help (VS Code tooltips)
- code_aster execution from VS Code
Goal : Harden existing features for daily production use.
- Harden the Language Server
- Improved parsing robustness
- Better error recovery
- Performance and memory optimizations
- Harden the
.exportfile generator- Validation of generated files
- Better error reporting
- Support for common real-world configurations
- Improve code_aster execution integration
- Clearer execution status and feedback
- Better handling of runtime failures
Goal : Improve user feedback and guidance inside VS Code.
- Open code_aster documentation directly from VS Code
- Command-level documentation lookup
- Context-aware links from auto-completion or diagnostics
- Parse code_aster log files
- Detect WARNING, ALARM, and ERROR
- Surface issues in the VS Code Problems panel
- Clickable navigation from diagnostics to source lines
- Improve error messaging and diagnostics consistency across the extension
Goal : Move from syntax assistance to domain-aware guidance.
- Enrich auto-completion with context and domain logic
- Context-aware suggestions based on :
- Command position
- Previously defined concepts
- Analysis type (static, modal, nonlinear, etc.)
- Detection of incompatible or suspicious command combinations
- Early feedback before execution
- Context-aware suggestions based on :
- Progressive validation of input files
- From syntactic → semantic → domain-level checks
- Full solver debugging
- Automatic model correction
- Non–code_aster solvers
- Results visualization
- Reduction of input-file related runtime errors
- Faster model setup for new users
- Increased adoption in real production workflows
- Positive feedback from experienced code_aster users
- Transparent roadmap and changelog
- Semantic versioning
- Backward compatibility when possible
- Community-driven improvements