You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that when formatting SQL with inline comments and leading commas, the formatter moves comments to the end of the previous line and changes the comma placement.
Example SQL I want to keep:
INSERT INTO sco_progress_log(
rec_datetime
,log_type
/* __CF_IF5__ */
,caller_sco_id
/* __CF_IF6__ */
,complete_date
)
SELECT
__CF_PARAM0__
,'rireki'
,NULL/* __CF_IF7__ */
,__CF_PARAM1__
/* __CF_IF8__ */FROM sco_progress ins_data
WHERE user_id = __CF_PARAM2__
AND course_id = __CF_PARAM3__
AND sco_id = __CF_PARAM4__
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Body:
Hi,
I noticed that when formatting SQL with inline comments and leading commas, the formatter moves comments to the end of the previous line and changes the comma placement.
Example SQL I want to keep:
Formatted result:
Issues:
/* __CF_IFx__ */
) are moved to the previous line instead of staying on their own line.Is there a way to preserve comment lines and leading commas? If not, could this be considered as a feature request?
Beta Was this translation helpful? Give feedback.
All reactions