Hi, dear reader,

notify is currently untested and I'd love to change that but I'll be straight up honest with you, I don't know how you test a library that's so dependent on external services. Like, do you create test/pseudo accounts/bots on all supported platforms and use the real api-tokens while testing? Do you actually make calls to the external services to verify the lib is working or can this be solved by mocking?

Feedback and PRs would be really appreciated! Hope you enjoy the library and have a nice day! :)

Description

Adding a toggle, that makes it possible to send E-Mails as unformatted Plain text.

Motivation and Context

I want to send E-Mails as unformatted Plain Text. Right now the mail service sends out e-mails as HTML only.

How Has This Been Tested?

• Tested locally using implementation.
• Added some tests to ensure fields are set correctly.

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Documentation (no code change)
• [ ] Refactor (refactoring production code)
• [ ] Other

Checklist:

• [x] My code follows the code style of this project.
• [ ] I have updated the documentation accordingly.
• [x] I have added tests to cover my changes.
• [x] All new and existing tests passed.

Description

add Bark service

Motivation and Context

add new service

How Has This Been Tested?

package main

import (
	"context"

	"github.com/nikoksr/notify"
	"github.com/nikoksr/notify/service/bark"
)

func main() {
	var device = "your bark key"
	// Create a bark service. `device key` is generated when you install the application
	barkService := bark.New(device, bark.DefaultServer)

	// Tell our notifier to use the bark service. You can repeat the above process
	// for as many services as you like and just tell the notifier to use them.
	notify.UseServices(barkService)

	// Send a test message.
	_ = notify.Send(
		context.Background(),
		"Subject/Title",
		"The actual message - Hello, you awesome gophers! :)",
	)
}

Screenshots / Output (if appropriate):

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Documentation (no code change)
• [ ] Refactor (refactoring production code)
• [ ] Other

Checklist:

• [x] My code follows the code style of this project.
• [x] I have updated the documentation accordingly.
• [ ] I have added tests to cover my changes.
• [x] All new and existing tests passed.

Description

Adds a notifier service for Mattermost

Motivation and Context

• Mattermost is an opensource alternative to slack. Mattermost has great community, supports various of tools integration, and also most of the features are FREE!
• Small teams can get great benefit from this messaging/collaboration service.

This addresses the issue https://github.com/nikoksr/notify/issues/422

How Has This Been Tested?

I tested this in 2 steps:

• Basic unit tests using mocks.
• Manual testing has been performed as well.

NOTE: make fmt introduced small change in mock_matrix_client.go file imports.

Screenshots / Output (if appropriate):

This is output from several runs.

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Documentation (no code change)
• [ ] Refactor (refactoring production code)
• [ ] Other

Checklist:

• [x] My code follows the code style of this project.
• [x] I have updated the documentation accordingly.
• [x] I have added tests to cover my changes.
• [x] All new and existing tests passed.

Description

Adds a notifier service for Matrix

Motivation and Context

This addresses #283 partially. I decided to split up the Matrix and Signal PRs as tey are two features in one ticket.

Matrix is an open standard and communication protocl for real-time communication.

How Has This Been Tested?

I tested this in 2 steps:

• Basic unit tests using mocks
• Manual testing has been performed as well

Screenshots / Output (if appropriate):

This is output from several runs.

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Documentation (no code change)
• [ ] Refactor (refactoring production code)
• [ ] Other

Checklist:

• [x] My code follows the code style of this project.
• [x] I have updated the documentation accordingly.
• [x] I have added tests to cover my changes.
• [x] All new and existing tests passed.

Add support for Instagram service.

I would be happy to add unit tests, but I skimmed through #1 and it seems like the decision on testing is still pending.

Description

Implement Viber service to solve #114

Motivation and Context

• This PR is to solve #114

How Has This Been Tested?

• Unit Test

• End-to-end testing

Screenshots / Output (if appropriate):

• Screenshot End to end testing The script that is used can be seen in the README with some modifications to change dummy values.

• Unit Test

• All Test Results There is a failure in syslog service but it's not related with this PR, maybe we can solve it in different PR?

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Documentation (no code change)
• [ ] Refactor (refactoring production code)
• [ ] Other

Checklist:

• [x] My code follows the code style of this project.
• [x] I have updated the documentation accordingly.
• [x] I have added tests to cover my changes.
• [ ] All new and existing tests passed.

Describe the solution you'd like The ability send message to specific recevier

telegramService, _ := telegram.New("your_telegram_api_token")
notify.UseServices(telegramService)

fooReceiver := telegram.Receiver(-1234567890)
barReceiver := telegram.Receiver(-0987654321)

// Send a message to fooReceiver .
_ = notify.To(fooReceiver).Send(
	context.Background(),
	"Hello",
	"The message to fooReceiver",
)
// Send another message to barReceiver 
_ = notify.To(fooReceiver).Send(
	context.Background(),
	"Hello",
	"The message to barReceiver",
)

Is your feature request related to a problem? Please describe.

Missing support for Viber.

Describe the solution you'd like

Implement a notification service and use existing services such as WhatsApp as a guide for implementation. At the time writing this, mileusna/viber seems to be the best client library for our service.

Is your feature request related to a problem? Please describe.

Presently when sending a notification, an error in sending to one receiver will cause stop all further messages. It would be nice if the service first attempted to notify to all other recievers.

package main

import (
    "github.com/nikoksr/notify"
    "github.com/nikoksr/notify/service/slack"
)

func main() {

    notifier := notify.New()

    // Provide your Slack OAuth Access Token
    slackService := slack.New("OAUTH_TOKEN")

    slackService.AddReceivers([]string{"INVALID_CHANNEL",  "VALID_CHANNEL"})

    notifier.UseService(slackService)

    // This will error on the first reciever ("INVALID_CHANNEL")
    // and the "VALID_CHANNEL" will never receive a message
    _ = notifier.Send(
        "Hello :wave:\n",
        "I am a bot written in Go!",
    )
}

Describe the solution you'd like

Either collate the errors and return them after all recievers have been attempted (i.e. add the errors to a slice), or find a more elegant way to collate meta-errors.

Pseudocode:

func ... Send(subject, message string) error {
	
     sendErrors := make([]string, 0, 0)

     for ... {
      
         if err != nil {
            sendErrors = append(sendErrors, errors.Wrapf(err, ...).Error())
            }
      }
      // This has the advantage of being "nil" in the case of no errors
      // but is perhaps inelegant / overly verbose
      if sendErrors != nil {
	  return errors.New(strings.Join(sendErrors, "\n"))
      }
      return nil
}

Describe alternatives you've considered

If errors are all expected to be of the same type, perhaps better to just collate the channel ids? I believe a similar field exists for all services.

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | github.com/sendgrid/sendgrid-go | require | minor | v3.11.1+incompatible -> v3.12.0+incompatible |

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, click this checkbox. ⚠ Warning: custom changes will be lost.

This PR has been generated by Mend Renovate. View repository job log here.

Fixes issue #459

Description

Implements Google Chat Service integration.

Motivation and Context

This PR solves Issue #459

How Has This Been Tested?

Decent unit test coverage

gocov test | gocov report
ok      github.com/nikoksr/notify/service/googlechat    0.384s  coverage: 85.2% of statements

github.com/nikoksr/notify/service/googlechat/mock_create_call.go                 newMockCreateCall               100.00% (4/4)
github.com/nikoksr/notify/service/googlechat/mock_spaces_message_creator.go      newMockSpacesMessageCreator     100.00% (4/4)
github.com/nikoksr/notify/service/googlechat/mock_create_call.go                 @55:12                          100.00% (1/1)
github.com/nikoksr/notify/service/googlechat/mock_spaces_message_creator.go      @41:12                          100.00% (1/1)
github.com/nikoksr/notify/service/googlechat/googlechat.go                       Service.AddReceivers            100.00% (1/1)
github.com/nikoksr/notify/service/googlechat/googlechat.go                       Service.Send                    88.89% (8/9)
github.com/nikoksr/notify/service/googlechat/mock_spaces_message_creator.go      mockSpacesMessageCreator.Create 85.71% (6/7)
github.com/nikoksr/notify/service/googlechat/mock_create_call.go                 mockCreateCall.Do               81.25% (13/16)
github.com/nikoksr/notify/service/googlechat/googlechat.go                       newMessageCreator               80.00% (4/5)
github.com/nikoksr/notify/service/googlechat/googlechat.go                       New                             80.00% (4/5)
github.com/nikoksr/notify/service/googlechat/googlechat.go                       messageCreator.Create           0.00% (0/1)
github.com/nikoksr/notify/service/googlechat                                     ------------------------------- 85.19% (46/54)

Total Coverage: 85.19% (46/54)

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Documentation (no code change)
• [ ] Refactor (refactoring production code)
• [ ] Other

Checklist:

• [x] My code follows the code style of this project.
• [x] I have updated the documentation accordingly.
• [x] I have added tests to cover my changes.
• [x] All new and existing tests passed.

Hello fellow Notify users!

We are the maintainers of the open source project Notify and we would love to know more about our community of users. If you are using Notify in your projects or at work, we would greatly appreciate it if you could share with us a brief description of how you are using it and any feedback you may have. This will help us understand the impact of our project and guide our future development efforts.

Thank you in advance for your contribution and happy holidays!

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | github.com/atc0005/go-teams-notify/v2 | require | minor | v2.6.1 -> v2.7.0 |

Release Notes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

Description

Adds support for Gotify.

Motivation and Context

Closes #455

How Has This Been Tested?

Unit tests are included.

Screenshots / Output (if appropriate):

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Documentation (no code change)
• [ ] Refactor (refactoring production code)
• [ ] Other

Checklist:

• [x] My code follows the code style of this project.
• [x] I have updated the documentation accordingly.
• [x] I have added tests to cover my changes.
• [x] All new and existing tests passed.

Description

Motivation and Context

There was feature request created in issue to add Ntfy service https://github.com/nikoksr/notify/issues/461

How Has This Been Tested?

Test program included in readme.md file

Screenshots / Output (if appropriate):

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Documentation (no code change)
• [ ] Refactor (refactoring production code)
• [ ] Other

Checklist:

• [x] My code follows the code style of this project.
• [x] I have updated the documentation accordingly.
• [ ] I have added tests to cover my changes.
• [x] All new and existing tests passed.