fix(generic): resolve ConfigFromWebhookURL regression causing 400 errors #398
  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.
  
    
  
    
This PR fixes a regression in the Generic service's
ConfigFromWebhookURLfunction that was causing 400 Bad Request errors when using webhook URLs with configuration parameters (like?template=json).Problem
The issue was reported in nicholas-fedor/watchtower#826 where 400 errors were experienced with Notifiarr notifications using the Generic service, while Discord notifications worked fine. The root cause was that config properties from webhook URL query parameters were not being set, causing incorrect defaults (plain text instead of JSON payloads).
Solution
SetConfigPropsFromQuerydirectly on unescaped query parameters after stripping custom values.Additional Changes
Changes