"Script as"-feature doesn't follow formatting configuration

[MartinRyx]

Issue Type: Bug

Right click a database object and select Script as Create (or Drop).

The generated script doesn't follow the casing settings (e. g. "mssql.format.keywordCasing"and "mssql.format.datatypeCasing") in settings.json.

It would be nice if the scripting functions used those settings.

Azure Data Studio version: azuredatastudio 1.35.1 (fab63efd307e54c063c8af03474bbb5d77f5fd11, 2022-03-15T18:03:38.261Z) OS version: Windows_NT x64 10.0.22000 Restricted Mode: No

System Info

Item	Value
CPUs	11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz (8 x 2995)
GPU Status	2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled skia_renderer: enabled_on video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	31.84GB (17.15GB free)
Process Argv
Screen Reader	no
VM	0%

[mkorsukov]

I experience the same issue. Here is a settings page:

But any automated / generated result is in UPPERCASE casing.

ALTER TABLE [dbo].[Bookkeeping] DROP CONSTRAINT [PK_Bookkeeping_LeadId] WITH ( ONLINE = OFF )
GO