Download the PHP package jaroslawzielinski/diagnostics-m2 without Composer
On this page you can find all versions of the php package jaroslawzielinski/diagnostics-m2. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download jaroslawzielinski/diagnostics-m2
More information about jaroslawzielinski/diagnostics-m2
Files in jaroslawzielinski/diagnostics-m2
Package diagnostics-m2
Short Description This module is for diagnostics in project
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package diagnostics-m2
Diagnostics-M2
a diagnostic module in magento2 project that can be used as a scaffolding for Your new code.
Why do you need this module in Your Project?
Introduction
Have you ever needed to...
- ...test/debug a part of Your code using separate controller in the backend area?
- ...test/debug a part of Your code using separate controller in the frontend area?
- ...test/change something in the database really quick using shell command?
- ...test some of Your frontend work like js/css/html in some separate place of the project and keep it there for some time?
- ...fix something in the project for some reason only locally and you did not know where to put it?
- ...do any from the above issues plus having dedicated configuration for it?
- ...do any from the above issues plus having the changes only in local env without repo modification?
If Your answer is yes for any of these, and additionally You recall it happend more then once or it happens often, please acknowledge that this diagnostic module is for You and is for free.
It will help You in Your work and You will find it usefull in any kind of magento2 project.
Overall idea of the module
You will install the core module via composer require --dev call. This way this module will not be in repo in the production mode.
You will override the core module by your own Vendor_Diagnostics module (The core module is only the basis for Your Custom Code added to Vendor_Diagnostics module).
You will add all of Your changes to .git/info/exclude if you are a git user:
What do You gain by using the Diagnostic Module?
You will have an easy way to test/debug backend controller (1.), frontend controller in new tab (2.) and view/edit Your dedicated configuration (3.) in the admin panel from the menu. You may do it all from one place, without affecting the repo (You may change Your branches, and the module will stay there, all the time unaffected...). See the screenshot below:
Also you have a CLI command that you may use/modify whatever way You like:
or after overriding getName and getDescription methods you may use e.g. this way:
How to install the Diagnostic Module via shell (1 Step out of 3)
in packagist
How to override the core module by Your Custom Code (2 Step out of 3):
Create a module:
Vendor/Diagnostics/registration.php
Vendor/Diagnostics/etc/module.xml
Override Admin Panel Configuration:
Vendor/Diagnostics/etc/adminhtml/system.xml
Vendor/Diagnostics/etc/config.xml
Vendor/Diagnostics/Model/Config.php
Override Console Command:
Vendor/Diagnostics/etc/di.xml
Vendor/Diagnostics/Model/Test/Customer.php
Override Controller Adminhtml Test:
Vendor/Diagnostics/etc/adminhtml/events.xml
Vendor/Diagnostics/Observer/Adminhtml/Test.php
Vendor/Diagnostics/Block/Adminhtml/Test.php
Vendor/Diagnostics/view/adminhtml/layout/JaroslawZielinski_diagnostics_diagnose_test.xml
Vendor/Diagnostics/view/adminhtml/templates/diagnose/test.phtml
Override Controller Test:
Vendor/Diagnostics/etc/frontend/events.xml
Vendor/Diagnostics/Observer/Test.php
Vendor/Diagnostics/Block/Test.php
Vendor/Diagnostics/view/frontend/layout/JaroslawZielinski_diagnostics_diagnose_test.xml
Vendor/Diagnostics/view/frontend/templates/diagnose/test.phtml
Hide Your Custom Code from git (3 Step out of 3)
Modify Your Vendor/Diagnostics module, add Your code there, use X Debug and...
...Enjoy Your coding!
One more usefull feature for Multistore
A little helper saying store details. Feature helping to acknowlege the Store parameters like route, name, id, code, locale and others. Available indicators:
- route (<route name>_<controller name>_<action name>)
- store_id
- store_code
- website_id
- store_name
- store_url
- is_store_active
- locale
Backend Configuration
Frontend
Another features added:
- Command
jaroslawzielinski:customer-without-password:create - Command
jaroslawzielinski:associated-products:find - Command
jaroslawzielinski:ssl-certificates:checkwith configuration in Admin Panel
