Describe your feature request

It would be great to use Pathlib Paths instead os.path...

For feature requests or questions, post on our Github Discussions page instead: https://github.com/ray-project/ray/discussions!

It looks like eval is a special case in our PHP parsing:

$ echo 'eval("echo foo");' | python -m semgrep --lang php --pattern 'evaz(...);' -
ran 1 rules on 1 files: 0 findings

$ echo 'eval("echo foo");' | python -m semgrep --lang php --pattern 'eval(...);' -
semgrep error: invalid pattern
  --> CLI Input:1
1 | eval(...);
  | ^^^^^^^^^

Pattern could not be parsed as a 

I'm sorry if I missed this functionality, but CLI version hasn't it for sure (I saw the related code only in generate_code_examples.py). I guess it will be very useful to eliminate copy-paste phase, especially for large models.

Of course, piping is a solution, but not for development in Jupyter Notebook, for example.

We noticed that we have some common patterns for common conflicts/duplicate resolution in our monorepo across different binaries.
Like

  deploy_jar_rules=jar_rules(rules=[
    Duplicate('^BUILD', Duplicate.SKIP),
    Duplicate('^META-INF/ASL2.0', Duplicate.SKIP),
    Duplicate('^META-INF/INDEX.LIST', Duplicate.SKIP),
    Duplicate('^META-INF/io.netty.versions.properties', Duplicate.SKIP