You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This could help track the code that created the implementation. If the layer has well-documented code (self-documented, a readme, or a link to Confluence), it would eliminate the need to rely on someone remembering it.
Expected Behavior
Once implemented, each resource should have a tag indicating the layer. This should aid in tracking the code that created the implementation.
Use Case
This feature is valuable for improving code traceability and documentation. It will provide a direct link between resources and the layer that created them, making it easier to understand and manage the codebase.
Describe Ideal Solution
The ideal solution would involve adding a tag to each resource during its creation, indicating the layer. The tag should be easily visible and accessible for reference. Consideration should be given to whether the tag can be obtained through a function or similar method to avoid the hardcoded example below.
An alternative could be to continue without these tags, relying on developers to remember or find the relevant layer for each resource. However, this could lead to inefficiencies and potential errors.
Additional Context
This feature request arose from a discussion about improving code traceability and documentation. The addition of a layer tag to each resource was suggested as a potential solution.
The text was updated successfully, but these errors were encountered:
Describe the Feature
Expected Behavior
Once implemented, each resource should have a tag indicating the layer. This should aid in tracking the code that created the implementation.
Use Case
This feature is valuable for improving code traceability and documentation. It will provide a direct link between resources and the layer that created them, making it easier to understand and manage the codebase.
Describe Ideal Solution
The ideal solution would involve adding a tag to each resource during its creation, indicating the layer. The tag should be easily visible and accessible for reference. Consideration should be given to whether the tag can be obtained through a function or similar method to avoid the hardcoded example below.
Alternatives Considered
An alternative could be to continue without these tags, relying on developers to remember or find the relevant layer for each resource. However, this could lead to inefficiencies and potential errors.
Additional Context
This feature request arose from a discussion about improving code traceability and documentation. The addition of a layer tag to each resource was suggested as a potential solution.
The text was updated successfully, but these errors were encountered: