-
Notifications
You must be signed in to change notification settings - Fork 97
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
Added project architecture sniffer docs #3014
base: master
Are you sure you want to change the base?
Added project architecture sniffer docs #3014
Conversation
docs/dg/dev/sdks/sdk/development-tools/project-architecture-sniffer.md
Outdated
Show resolved
Hide resolved
docs/dg/dev/sdks/sdk/development-tools/project-architecture-sniffer.md
Outdated
Show resolved
Hide resolved
docs/dg/dev/sdks/sdk/development-tools/project-architecture-sniffer.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Andrey Tkachenko <andrey.tkachenko@spryker.com>
--- | ||
title: Project Architecture Sniffer | ||
last_updated: Jan 7, 2024 | ||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add description and template
|
||
This tool ensures that your project's architecture aligns with Spryker's best practices and guidelines. | ||
|
||
## Priority levels |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add the context for prio levels
|
||
{% info_block infoBox %} | ||
|
||
Spryker demo shops may contain violations when analyzed with the Architecture Sniffer, as the tool includes more project specific rules by default. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How are the demo shops related to project level rules?
PR labels
When the PR is ready for review, add a TW review needed label. This lets us keep track of PRs that need to be merged and merge them in time.
PR Description
Describe the context for your changes and the changes you've made.
Tickets
If changes are associated with a ticket, add a docs ticket here.
Checklist