Bumping this issue as the style guide has been updated in compliant to the above changes, and the LS should provide solutions that reflect the best practices. ballerina-platform/ballerina-dev-website#8884.

Simply removing the type symbol is not straightforward, as the code action may generate erroneous code in some scenarios. For instance, consider the following scenario, which generates an incompatible error.

function foo(decimal val) {}

// Extracts the following value
foo(12)

// Generates the following code
const CONST = 12 // which is inferred as int

The ideal solution would be to manually consider such cases and add the d prefix to such values. However, this imposes a performance bottleneck on the code action, and the scalability is also fragile since there can be more such cases once we expand the support for constants.