Fix explanation on `.` in the `REST service - Service and resource paths` BBE
praneesha opened this issue · comments
Description
Need to fix the explanation below on .
in the REST service - Service and resource paths
BBE.
// The
.represents the current resource that is
/info.
![Screenshot 2024-02-26 at 15 40 14](https://private-user-images.githubusercontent.com/11707273/307747070-f5cf44b5-6ffb-45e0-8769-1c0caaba6cdd.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk3MDk3NDQsIm5iZiI6MTcxOTcwOTQ0NCwicGF0aCI6Ii8xMTcwNzI3My8zMDc3NDcwNzAtZjVjZjQ0YjUtNmZmYi00NWUwLTg3NjktMWMwY2FhYmE2Y2RkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MzAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjMwVDAxMDQwNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTE5YzQwYzQ2YzhjMWYzNTliMThiOWRjZTk4N2ZiYmMzODRiNjEwMTQ4NmQ5YzZjOTMzOTJjMjhmMDM1ZjkyNGUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.y52NqvgbDTLavYBnyf9V2NYLtriQHkF-obDpH3WU2wQ)
Steps to reproduce
The steps to be followed to reproduce the issue.
Affected version(s)
The versions that are affected by the issue.
Related website/documentation area
Add/Uncomment the relevant area label out of the following.
Related issue(s) (optional)
Any related issues such as sub tasks and issues reported in other repositories (e.g., component repositories), similar problems, etc.
Suggested label(s) (optional)
Optional comma-separated list of suggested labels. Non committers can’t assign labels to issues, and thereby, this will help issue creators who are not a committer to suggest possible labels.
Suggested assignee(s) (optional)
Optional comma-separated list of suggested team members who should attend the issue. Non committers can’t assign issues to assignees, and thereby, this will help issue creators who are not a committer to suggest possible assignees.
@TharmiganK any update on this?
@TharmiganK any update on this?
@anupama-pathirage I could not be able to work on this since I am working on some priority features with Update 9. Is it ok to fix this after the code freeze (4th April, 2024)?
@TharmiganK any update on this?
@anupama-pathirage I could not be able to work on this since I am working on some priority features with Update 9. Is it ok to fix this after the code freeze (4th April, 2024)?
Yes, lets get it fixed after code freeze.