Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After only 1 year stuck on my PC...
This pull request introduces updates to the
nutgram/nutgramdependency, adds a new console command for development purposes, and refactors how Telegram routes are loaded in the service provider. Below are the most important changes grouped by theme:Dependency Update:
nutgram/nutgramdependency incomposer.jsonfrom version^4.17.0to^4.20to ensure compatibility with the latest features and fixes.New Feature:
ListenCommandclass insrc/Console/ListenCommand.phpto enable development-friendly bot listening with automatic reloads after every update. This command is intended for development only and warns against use in production environments.Service Provider Enhancements:
registermethod inNutgramServiceProviderto dynamically load Telegram routes when thenutgram.routesconfiguration is enabled. This replaces the previous approach of loading routes directly in thebootmethod.ListenCommandin thebootmethod ofNutgramServiceProvider, making it available as part of the application's console commands.bootmethod ofNutgramServiceProvider, as it is now handled during the resolution of theNutgraminstance.