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.

Sign up for GitHub

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

Jump to bottom

MEC Exposure & Experience Management ressource names don't follow naming conventions or are not descriptive enough #151

Open
leochely opened this issue Nov 10, 2023 · 1 comment
Open

MEC Exposure & Experience Management ressource names don't follow naming conventions or are not descriptive enough #151

leochely opened this issue Nov 10, 2023 · 1 comment
Assignees
@maheshc01

Comments

@leochely
Copy link
Collaborator

leochely commented Nov 10, 2023 •
edited
Loading

I have noticed that certain resource names do not adhere to the established naming conventions defined in the API Design Guidelines. Specifically, I would like to address the following resource names:

  • MECPlatforms -> mecPlatforms
  • serviceProfileID -> serviceProfileId
  • zone -> zoneId
  • region -> regionId
  • ecspFilter -> preferredEdgeProvider
  • ern -> edgeResourceName

To maintain uniformity and clarity in our codebase, I propose that we update these resource names to follow the lower camel case naming convention.
@leochely leochely changed the title MEC Exposure & Experience Management ressource names don't follow naming conventions MEC Exposure & Experience Management ressource names don't follow naming conventions or are not descriptive enough Nov 28, 2023
Closed
@leochely leochely mentioned this issue Dec 6, 2023
Closed
@Kevsy
Copy link
Collaborator

Kevsy commented Dec 11, 2023

@maheshc01 please could you take a look at this one?

maheshc01 added a commit to maheshc01/EdgeCloud that referenced this issue Jun 11, 2024
@maheshc01
fixes camaraproject#38 and camaraproject#151
786d8ff
@maheshc01 maheshc01 mentioned this issue Jun 11, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@maheshc01 maheshc01

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Kevsy @leochely @maheshc01