use of filename starting with "self" breaks sonar analysis

[ansghof]

In our project, we have a file called "self_service.rs" which is (obviously) a self service api for users to do stuff themselves. The file is called self_service and thus the import also calls it that. Unfortunately, the parser seems to break here, presumably because it thinks it encountered a "self" keyword at an unexpected position. The following code will break sonar analysis:

 1: use actix_web::web::Data;
 2: ... <redacted>
 3: 
 4: use crate::{
 5:     api::self_service::SomeStruct,
                 ^
...
 9: };
10: use std::fmt::Write;
11: 
12: pub fn function_at_the_start_of_the_source_file(
...
08:47:36.674 ERROR Unable to parse file: rust/api/src/service/failed_to_parse.rs
08:47:36.674 ERROR Parse error at line 5 column 14:

In theory, any import that starts with self will fail. Somehow the lexer seems to think that this is a self keyword.

[ansghof]

Add this test in RustLexerTest.java:

  @Test
  void testSelfInsideImportTokens() {
    String filename = "selfish";
    String sexpr = "\n" +
        "use api::" + filename + "::MyService; \n" +
        "       fn update_rates(){" +
        "             todo!()\n" +
        "             }";

    ParserAdapter<LexerlessGrammar> parser = new ParserAdapter<LexerlessGrammar>(StandardCharsets.UTF_8,
        RustGrammar.create().build());
    parser.parse(sexpr);
  }

Fails for:

• filename = "self_service";
• filename = "selfish";

Works for:

• filename = "my_self";
• filename = "unselfish";

[C4tWithShell]

Hi! Thanks for reporting it, I will work on fix

[ansghof]

Thanks for the quick response, the fix looks good to me. I'll be eagerly waiting for 0.2.6 to be released and then annoy our sonarqube admins to update asap.

[ansghof]

My plugin was updated and the errors have vanished. Thank you @C4tWithShell !