Stuck on an issue?
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.
Add support for binding boolean parameters to variables
See original GitHub issueIf you create a task with a boolean input parameter, there appears to be no way to use that task in a build/release and bind the value to a variable.
This would be similar to making a pickList input parameter editable: "EditableOptions": "true".
Thanks!
Issue Analytics
- State:
- Created 7 years ago
- Comments:16 (16 by maintainers)
Top Results From Across the Web
bind_param problem with binding boolean values
When I remove the read field in the statement everything works fine. I've run out of ideas with this one. Surely bind_param works...
Read more >bind_variable with boolean type - Oracle Communities
Hi all, I need to use dbms_sql to invoke a PL/SQL procedure. The problem is that a parameter of this procedure is a...
Read more >Binding CheckButton with boolean variable
Hello, Is it possible to bind CheckButton property "Checked" with boolean variable? No success and couldn't find such help on the internet.
Read more >Model Binding in ASP.NET Core | Microsoft Learn
Finds the next parameter of GetById , a boolean named dogsOnly . Looks through the sources and finds "DogsOnly=true" in the query string....
Read more >Binding a controll parameter to a Porlet Include preference
I need to pass this variable to the portlet included. So what I did is add a control parameter to Portlet Include Control...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
That seems unfortunate, it seems more intuitive to use params (and simpler, I don’t need to load and learn how to use a custom ps module). It is also easier to test and easier to re-use outside of VSTS tasks. Also, I love typescript, but the simplicity of not having to compile anything is convenient, too, and I don’t think cross platform task support gives me any benefit when building/deploying web apps targeting Azure PaaS offerings. It also seems plausible that someday powershell runs on Linux. If I stick with powershell (not sure if I will), these would be the reasons why.
I am sure there are situations where additional features are needed that are not supported by what I just described, but I have written a number of custom tasks and have yet to encounter a need for anything more complex, and I prefer to keep things as simple as possible when possible.
Since you call this handler legacy, do you already consider it deprecated? Thanks!
Based on the original context it sounds like this issue can be closed. I don’t think there is an issue here. Feel free to reopen or start a new issue if my interpretation is incorrect.