[2201.3.x] Update visible endpoint generation to identify client object files with annotations #39502
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
Update visible endpoint generation to identify
client object
files with annotations.Fixes #39657
Approach
Semantic API doesn't send CLIENT qualifier for
client object node
with annotations. This PR will skip annotation from the node and request Semantic TypeSymbol just only for theclient object
.In the above example
@display { label: "InternalClientService", } InternalClient inEp3
node won't get the CLIENT qualifier. But just creating a new node withInternalClient inEp3
will send the CLIENT qualifier.Remarks
Check List