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
I would like to bring to your attention that some projects within the repository, such as Basket.API, do not follow the eShop.* naming convention for default namespaces. Here are the details and a suggestion for improvement:
Current Namespace Configurations
Example: The Basket.API project, among others, does not align with the common eShop.* pattern. This inconsistency is depicted in the attached screenshot.
Impact on Visual Studio Integration
Description: This variance in namespace naming can complicate the automatic syncing process with Visual Studio, potentially impacting development flow and consistency.
It would be beneficial to standardize the namespaces across projects to the eShop.* pattern. If the team finds it helpful, I'm more than willing to assist by contributing a pull request to make this adjustment.
The text was updated successfully, but these errors were encountered:
I would like to bring to your attention that some projects within the repository, such as Basket.API, do not follow the eShop.* naming convention for default namespaces. Here are the details and a suggestion for improvement:
Current Namespace Configurations
Example: The Basket.API project, among others, does not align with the common eShop.* pattern. This inconsistency is depicted in the attached screenshot.
Impact on Visual Studio Integration
Description: This variance in namespace naming can complicate the automatic syncing process with Visual Studio, potentially impacting development flow and consistency.
It would be beneficial to standardize the namespaces across projects to the eShop.* pattern. If the team finds it helpful, I'm more than willing to assist by contributing a pull request to make this adjustment.
The text was updated successfully, but these errors were encountered: