@@ -238,8 +238,8 @@ private Optional<String> parseProperty() {
238238 }
239239
240240 if (discard ) {
241- // Whitespace is significant inside property expressions, but it's impossible to
242- // define properties with spaces, so expressions with spaces always evaluate to "".
241+ // Whitespace is significant inside property expressions, but it's impossible to define
242+ // properties with spaces, so expressions with spaces always evaluate to "".
243243 return Optional .of ("" );
244244 } else {
245245 return Optional .of (state .getProperty (ident .get ()));
@@ -264,8 +264,8 @@ private Optional<String> parseMetadata() {
264264 }
265265
266266 if (discard ) {
267- // Whitespace is significant inside metadata expressions, but it's impossible to
268- // define metadata with spaces, so expressions with spaces always evaluate to "".
267+ // Whitespace is significant inside metadata expressions, but it's impossible to define
268+ // metadata with spaces, so expressions with spaces always evaluate to "".
269269 return Optional .of ("" );
270270 } else if (metadataProvider != null ) {
271271 return Optional .of (metadataProvider .apply (ident .get ()));
@@ -324,10 +324,9 @@ private boolean skipWhitespace() {
324324
325325 private void unsupportedFeature (String feature ) {
326326 // We don't know the relative importance of this expression - it could be an expression that
327- // SonarDelphi
328- // never needs to read. Making this a warning despite having a well-defined behaviour for when
329- // an unsupported
330- // feature is encountered (to interpret it literally) would probably be overkill.
327+ // SonarDelphi never needs to read. Making this a warning despite having a well-defined
328+ // behaviour for when an unsupported feature is encountered (to interpret it literally) would
329+ // probably be overkill.
331330 LOG .debug ("Unsupported MSBuild feature '{}' ignored in expression: {}" , feature , text );
332331 }
333332}
0 commit comments