Comments
Sort by recent activity
It seems that the extension returned on its own yesterday. I will save your comment though. Since the issue seems to be recurring I can check if this works at a later point and update this thread. / comments
It seems that the extension returned on its own yesterday. I will save your comment though. Since the issue seems to be recurring I can check if this works at a later point and update this thread.
Hi, I attached it here as a txt file (json isn't allowed as an attachment here). I also noticed something else; If a procedure call has named paramters, it gets formatted correctly. However, if the parameters are unnamed, it gets formatted on one line. I hope this helps you zoom in on the issue. / comments
Hi, I attached it here as a txt file (json isn't allowed as an attachment here). I also noticed something else; If a procedure call has named paramters, it gets formatted correctly. However, if the...
The final fix seemed to have worked, thanks! / comments
The final fix seemed to have worked, thanks!
Good day, I tried this, and I realized that the issue lies with what the code formatting recognises as lists. An example - I have a call to a stored procedure which gets formatted correctly with those settings, like this: EXEC UTILS.dbo.Procedure @param1 , @param2 , @param3 OUTPUT , @param4 OUTPUT , @param5; Then later on in this same code block I have another procedure call, but it gets formatted like this:
EXEC UTILS.dbo.Procedure2 @param1, @param2, @param3 = 0; So where does this difference come from? / comments
Good day, I tried this, and I realized that the issue lies with what the code formatting recognises as lists. An example - I have a call to a stored procedure which gets formatted correctly with th...
I may be double posting this, but I feel like the forum ate my previous reply. I tried with those settings, but I realized the issue lies with what the formatting recognizes as lists. One procedure call with parameters gets recognized as a list, another isn't. Example This works well: EXEC UTILS.dbo.Procedure @param1 , @param2 , @param3 OUTPUT , @param4 OUTPUT , @param5;
This gets formatted on one line: EXEC UTILS.dbo.Procedure2 @param1, @param2, @param3 = 0; / comments
I may be double posting this, but I feel like the forum ate my previous reply. I tried with those settings, but I realized the issue lies with what the formatting recognizes as lists. One procedure...