Extract resource name for http filters

[ldclakmal]

Purpose

The resourceNode.name.value is evaluated as the resource name concatenated with the accessor and $ symbols. In order to engage HTTP filters, the exact resource name should be desugard in to the HTTP filter context.

Example 1:
resource function get sayHello is evaluated as "$get$sayHello" and converted by the PR as "sayHello"

Example 2:
resource function myAccessor sayHello is evaluated as "$myAccessor$sayHello" and converted by the PR as "sayHello"

Example 3:
resource function my\$Accessor say\$Hello is evaluated as "$my\$Accessor$say\$Hello" and converted by the PR as "sayHello"

Related to #27820
Related to ballerina-platform/ballerina-library#584

Check List

• Read the Contributing Guide
• Updated Change Log
• Checked Tooling Support (#)
• Added necessary tests
  • Unit Tests
  • Spec Conformance Tests
  • Integration Tests
  • Ballerina By Example Tests
• Increased Test Coverage
• Added necessary documentation
  • API documentation
  • Module documentation in Module.md files
  • Ballerina By Examples

[rdhananjaya]

Is this method supposed to extract the resource paths?
say we have a resource function such as resource function get foo/bar/[int i]/[int j]() { } what is the expected behavior?

[ldclakmal]

The objective of this function is to extract the resource name by removing the accessor part attached to it. The expected value for the given resource signature is "foo$bar$*$*" and this function returns that.

[rdhananjaya]

Ack, I was confused with the term resourceName as resource functions doesn't have a name anymore. Shall we concatenate the text parts of this instead of removing from the generated string.

[ldclakmal]

The resourceNode.name.value is evaluating is correct according to the new service type changes. It should be fixed at ballerina/reflect module.
Related issue: ballerina-platform/ballerina-library#837