Current formatting is:

CASE
WHEN 1 = 1 THEN
'Hello World'
END

I need the option to put the expression on the same line:

CASE
WHEN 1 = 1 THEN 'Hello World'
END

Is it possible to add a hard return after the /* comment */ block so code doesn't keep formatting after the comment

Currently:
/* comment */ UPDATE User
SET Modified = CAST('2018-12-20' AS datetime)
WHERE id = 255454

Suggestion
/* comment */
UPDATE USER
SET Modified = CAST('2018-12-20' AS datetime)
WHERE id = 255454

I updated to SQL Prompt 9.4.7.7595 yesterday and since then I no longer have the hot key. It is still on the menu, but no hotkey. I used that feature hourly. If you wish, allow users to define the hotkey combinations or disable them, but simply removing them is inconvenient.

If a sql command is written with an APS specific statement (for example: "CREATE TABLE AS, or "OPTION (Label = 'Query Description')" ), then a script parsing error appears.

SQL Prompt should be able to Visualize the Code and represent the code like Flow Chart.
This Feature will be very useful while working with heavy Stored Procedures.
The Sample Code Visualization image is shared below:
--
https://drive.google.com/file/d/1dE0H7UP1MOuOZ4A3e4urUkDlR0FD4474/view?usp=sharing
--

Issue code SC003 shouldn't happen if the USE statement is at the top of a SQL script.

Please add an option be added to SQL Prompt to trim all white space.

Ideally, the following would be supported:
- Ability to execute against a query window or block of selected code
- Available as a stand-alone shortcut
- Can include as part of a Format SQL style
- Option to remove a) leading spaces, b) trailing spaces, c) both

Currently, SQL Prompt either allows you to apply casing all at once with the Apply Casing Options, or it does it as you type if Enable Suggestions is turned on.

Please add a feature so that I can have casing applied as I type, but without the suggestions.

If you have a table declared like this:
Declare @Test table
(TheKey int Primary Key,
SomeData varchar(10) Not Null)

I am told that for "TheKey" "[NOT] NULL option is not specified in CREATE/DECLARE TABLE statement" defined. But, a Primary Key can never be null, so it is NOT NULL by nature.

So, when performing Code Analysis and the parser sees "Primary Key", "Not Null" should be inferred also.

Some people uses the latest versions of SSMS. I'd like to see it in non-release versions, maybe not fully supported yet.

The Format SQL command currently overlooks these keywords and they end up appended to the last line of the ORDER BY clause. Ideally, I'd like to have the option to place both OFFSET and FETCH NEXT on separate lines, aligned just like the SELECT, FROM, WHERE, and ORDER BY keywords.

We have adopted SCG and have commented out areas of code we do not want checking with scgignore. The new version of SCG command prompt and SQL Prompt do not recognise these comments, and report the area of code with warnings.
Please amend so they are not reported, or at least reported differently so we can ignore.

I would like to be able to better automate our onboarding process for new developers by helping ensure their snippets folder, formatting style folder and default formatting style are correctly setup. Additionally we would like to be able to automatically import settings from UNC/source control for them. This reduces the inevitability that something is missed when trying to follow a setup guide we have to additionally maintain. Thanks!

I'd like to vote for adding ST008 (non-named parameter style used) to the issues which can be auto-fixed. Hopefully it would be fairly simple to implement.

It would be nice if the "Encapsulate as new stored procedure" logic used named parameter style so I don't immediately get ST008 in my code which calls the new proc.