Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix explanation on . in the REST service - Service and resource paths BBE #8734

Closed
praneesha opened this issue Feb 26, 2024 · 5 comments
Closed
Assignees
Labels
Category/Content All written content related issues (Technical content, english language etc) Reason/EngineeringMistake Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Type/Bug Bugs that need to be fixed.

Comments

@praneesha
Copy link

praneesha commented Feb 26, 2024

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

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.

@praneesha praneesha added the Type/Bug Bugs that need to be fixed. label Feb 26, 2024
@anupama-pathirage
Copy link
Contributor

@TharmiganK any update on this?

@TharmiganK
Copy link
Contributor

@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)?

@anupama-pathirage
Copy link
Contributor

@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.

@TharmiganK
Copy link
Contributor

Fixed with the above PRs

Copy link

This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
      - Reason/Regression - The issue has introduced a regression.
      - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
      - Reason/Complex - Issue occurred due to complex scenario.
      - Reason/Invalid - Issue is invalid.
      - Reason/Other - None of the above cases.

@TharmiganK TharmiganK added the Reason/EngineeringMistake Reason/EngineeringMistake The issue occurred due to a mistake made in the past. label Jul 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category/Content All written content related issues (Technical content, english language etc) Reason/EngineeringMistake Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Type/Bug Bugs that need to be fixed.
Projects
Archived in project
Development

No branches or pull requests

3 participants