@@ -143,17 +143,18 @@ The Solidity versions taken into consideration during formatting are:
143143
144144 ``` Solidity
145145 // Input
146- import { Foo as Bar } from "/an/extremely/long/location";
146+ import { Foo as Bar, Baz as Qux } from "/an/extremely/long/location";
147147
148- // "compiler": undefined
149- import { Foo as Bar } from "/an/extremely/long/location";
148+ // { "compiler": undefined, parser: "antlr" }
149+ import { Foo as Bar, Baz as Qux } from "/an/extremely/long/location";
150150
151- // "compiler": "0.7.3" (or lesser)
152- import { Foo as Bar } from "/an/extremely/long/location";
151+ // { "compiler": "0.7.3" (or lesser) }
152+ import { Foo as Bar, Baz as Qux } from "/an/extremely/long/location";
153153
154- // "compiler": "0.7.4" (or greater)
154+ // { "compiler": "0.7.4" (or greater) }
155155 import {
156- Foo as Bar
156+ Foo as Bar,
157+ Baz as Qux
157158 } from "/an/extremely/long/location";
158159 ```
159160
@@ -208,9 +209,9 @@ You might have a multi-version project, where different files are compiled with
208209}
209210```
210211
211- | Default | CLI Override | API Override |
212- | ------- | --------------------- | ---------------------- |
213- | None | ` --compiler <string> ` | ` compiler: "<string>" ` |
212+ | Default | CLI Override | API Override |
213+ | --------------------------------------------------------------------------------------------- | --------------------- | ---------------------- |
214+ | Inferred from pragma statements when using parser ` slang ` < br /> None when using parser ` antlr ` | ` --compiler <string> ` | ` compiler: "<string>" ` |
214215
215216### Parser
216217
0 commit comments