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

The retail spec does not have the standard enums defined for various string types #13

Open
rajaneeshk90 opened this issue Jan 16, 2024 · 0 comments

Comments

@rajaneeshk90
Copy link

Issue Details:

Problem Statement:
The current retail specification lacks a well-defined structure for handling enumerations (enums), leading to potential confusion for developers. Enumerations are essential for maintaining a consistent set of values, and a standardized approach is needed for better spec organization.

Proposed Solution:
Establish a clear and standardized structure for handling enums within the retail spec. Create a dedicated "Enums" directory within api subdirectory for enums that are utilized. This subdirectory should contain the relevant enum files, appropriately named and documented.

Benefits:

  1. Enhanced Spec Organization: A well-structured "Enums" directory will improve the organization of enum definitions, making it easier for developers to locate and maintain them.
  2. Ease of Reference: The organized enum structure allows for quick and efficient reference, benefiting developers who need to work with or extend existing enumerations.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant