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

Log feedback #139

Open
jhadobe opened this issue Dec 13, 2024 · 1 comment
Open

Log feedback #139

jhadobe opened this issue Dec 13, 2024 · 1 comment
Labels
best-practices Content related to Commerce implementation best practices topics

Comments

@jhadobe
Copy link
Contributor

jhadobe commented Dec 13, 2024

We received the following feedback about Write to custom log.

"Step 3 in ""Set up a custom log file in the di.xml"" suddently talks about injecting into a new class without talking about what the class does, forcing the reader to go to that class in code which may or may not still contain the code intended for this example.
Step 4 of the same section seems to just repeat information in Step 2 in a really confusing way that makes it seem like additional code needs to be written which is not the case."

@atwixfirster it looks like you created this page in this PR. Can you submit a PR or suggest any guidance to address the issue? The file is currently located here: https://github.com/AdobeDocs/commerce-operations.en/blob/main/help/configuration/logs/custom-log-files.md.

@jhadobe jhadobe added the best-practices Content related to Commerce implementation best practices topics label Dec 13, 2024
@github-jira-sync-bot
Copy link
Collaborator

✅ Jira issue COMDOX-1141 is successfully created for this GitHub issue.

@github-project-automation github-project-automation bot moved this to 🆕 Ready for Grooming in Commerce - Issues Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
best-practices Content related to Commerce implementation best practices topics
Projects
Status: 🆕 Ready for Grooming
Development

No branches or pull requests

2 participants