Comments (6)
@garymm Thanks for the ticket, I am not familiar with ${workspaceFolder}
is this something that the newer vscode api's provide to the extension settings? (@mattseddon might have insights here as well if the extension needs to consider some template like variables?)
from vscode-coverage-gutters.
Visual Studio Code supports variable substitution in Debugging and Task configuration files as well as some select settings. Variable substitution is supported inside some key and value strings in launch.json and tasks.json files using ${variableName} syntax.
source https://code.visualstudio.com/docs/editor/variables-reference
You could make it work but it would definitely not be free.
The best (quickest) option for low maintenance is to specify in the docs/description of the config option (coverage-gutters.manualCoverageFilePaths
) that the path provided must be a full path. I don't think this would lead to terrible UX because the option only has to be set once.
from vscode-coverage-gutters.
Visual Studio Code supports variable substitution in Debugging and Task configuration files as well as some select settings. Variable substitution is supported inside some key and value strings in launch.json and tasks.json files using ${variableName} syntax.
source https://code.visualstudio.com/docs/editor/variables-reference
You could make it work but it would definitely not be free.
The best (quickest) option for low maintenance is to specify in the docs/description of the config option (
coverage-gutters.manualCoverageFilePaths
) that the path provided must be a full path. I don't think this would lead to terrible UX because the option only has to be set once.
Thanks @mattseddon sounds like a good option on the documentation front.
from vscode-coverage-gutters.
This unfortunately precludes sharing these settings with a team. We're actually running into this issue right now, where we want to put these setting into our versioned ${repo}/.vscode/settings.json
like we do with certain other settings ("eslint.workingDirectories"
, "java.checkstyle.version"
, etc.).
Are we open to accepting a PR to support either ./...
or ${workspaceFolder}/...
?
from vscode-coverage-gutters.
I can't speak for @ryanluker but I would say that if you are sharing settings/extensions with a team then a good option is to create a shared dev container.
https://code.visualstudio.com/docs/devcontainers/create-dev-container
from vscode-coverage-gutters.
This unfortunately precludes sharing these settings with a team. We're actually running into this issue right now, where we want to put these setting into our versioned
${repo}/.vscode/settings.json
like we do with certain other settings ("eslint.workingDirectories"
,"java.checkstyle.version"
, etc.).Are we open to accepting a PR to support either
./...
or${workspaceFolder}/...
?
@josephzidell Thanks for the input! The repo is very open for PRs to add extra support as long as the tests pass and the performance isn't worsened for the other path use cases.
Take a look at @mattseddon 's suggestion first though and see if that fills your needs 🤔.
from vscode-coverage-gutters.
Related Issues (20)
- Coverage "gutter" not showing, "line" and "ruler" OK HOT 8
- Extension settings do not have the scope property defined HOT 3
- refactoring if clause caused extension to crash HOT 3
- update CHANGELOG.md to make changes extension-visible
- Java example pom issues and failure in mvn install HOT 2
- Cannot seem to watch files outside of VS Code workspace directory HOT 2
- Improve visibility of covered lines HOT 4
- Add support for remote coverage files HOT 3
- Support coverage reports with multiple sources HOT 2
- behavior change suggestion/rfc: statusbar should report `Math.floor` instead of `Math.round` HOT 1
- `Illegal argument: line must be non-negative` when any `detail.line` is 0 HOT 1
- Where does the watcher look for the lcov.info file? HOT 2
- Coverage information fails to render when branch coverage is enabled HOT 1
- Update deploy automation action to use v1 of external action
- Cant read coverage data from cobertura-coverage.xml HOT 1
- Don't highlight tested lines HOT 4
- vsix packaging: drop unused folders HOT 1
- cobertura Status Bar Percentage Wrong with C# Workspace HOT 6
- Attempting to parse cobertura.xml fails after converting from visual studio .coverage binary. HOT 2
- settings: resolve configuration settings HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vscode-coverage-gutters.