Describe the bug
The project file contains the configuration section. This is always present and is filled with the local general settings. If this project file is checked into a VCS and checked out on a different machine, tool like linter etc. are very much likely not configured correctly because the paths on the other machine differ.
Perhaps this a feature and not a bug, but it makes it difficult using TerosHDL in a team.
To Reproduce
Save project file and examine the YAML file. It always contains the section configuration including local paths.
Code
n/a
Please complete the following information:
- OS: Windows 11
- VSCode version 1.106.0
Screenshots
n/a
Additional context
There are a couple of options to solve the issue.
- don't save paths in the configuration
- let the user select if the configuration should be saved with the project
- just save the differences from global settings
Each suggestion has draw-backs of course. I am happy to discuss the options ;-)
Describe the bug
The project file contains the configuration section. This is always present and is filled with the local general settings. If this project file is checked into a VCS and checked out on a different machine, tool like linter etc. are very much likely not configured correctly because the paths on the other machine differ.
Perhaps this a feature and not a bug, but it makes it difficult using TerosHDL in a team.
To Reproduce
Save project file and examine the YAML file. It always contains the section configuration including local paths.
Code
n/a
Please complete the following information:
Screenshots
n/a
Additional context
There are a couple of options to solve the issue.
Each suggestion has draw-backs of course. I am happy to discuss the options ;-)