Bug when formatting float literals in BigQuery

[liaopeiyuan]

Describe the bug
sqlfmt adds unnecessary spaces for float literals in E notation in BigQuery

To Reproduce
1e-9

Expected behavior
1e-9

Actual behavior
1 e -9

Additional context
We are using the sqlfmt embedded in dbt develop. The UI on https://sqlfmt.com/ produces the same result.

[tconbeer]

Thanks for the report, @liaopeiyuan . I knew, and then forgot, that number literals could use scientific notation. This is true in postgres too. This is definitely a bug; I'll get this fixed asap.

We just need to change the number Rule to add a pattern that will match something like 1e-9 or -55.55e10. Decimals after the e are not supported (at least on pg).

sqlfmt/src/sqlfmt/rules/core.py

Lines 70 to 76 in f349abe

	Rule(
	name="number",
	priority=350,
	pattern=group(
	r"-?\d+\.?\d*",
	r"-?\.\d+",
	),

Snowflake docs include a pseudo-regex, which is really helpful: https://docs.snowflake.com/en/sql-reference/data-types-numeric.html#numeric-constants

[tconbeer]

@liaopeiyuan This patch has been merged to main. Thanks again for the report!