Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Is there a way to define custom properties in task.json and consume those in the build task?
See original GitHub issueIs there a way to define a static custom property in task.json and consume that in the associated (PowerShell) build task? This would not be a user editable input.
We have multiple TFS environments and the property of the task only needs to vary between environments. My thought is that at the point the task is uploaded, our deployment process could set the property in task.json to the value specific to the environment. Or would you recommend an alternative approach?
Hope this makes sense. Thanks
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@damccorm I ended up writing a separate config.json file which is read by the build step, The values in the config.json are modified by our deployment process that packages up the build step and pushes it to our TFS instances.
Well I think having it defined in the task.json would be nicer, either in its own config/options section or as an input with a default value that isn’t editable / hidden