Allow Notifynder builder to add custom data

[fenos]

At this stage NotifynderBuilder doesn't allow easily to add custom values for custom columns into the notifications table. That is caused from the setBuilderData to be protected.
Once the function will be publicly usable, the developer will have the opportunity to extend the table (if needed).

Another move related to this issue, will be to have a minimal required validation on this new custom fields, so that the developer can define his custom fields to be globally required at any time.

[Gummibeer]

PR #106 is merged so this is done & closed

[awgv]

@Gummibeer
@fenos

Hey,

Can you please give an example on how to set values for additional fields? I added a field in the migration file, then in the config:

    'additional_fields' => [
        'required' => [
            'label'
        ],
        'fillable' => [
            'label'
        ],
    ],

But how are you supposed to set its value to something? I thought maybe I should try to build a notification using an array or properties, but I didn’t understand what $notifynder = $this->notifynder; should be pointing at. setBuilderData() returns a $notifications key, and you can’t chain it. What am I missing?

Also, I was able to create a notification without specifying a label field after adding it to required array in the config (although, label is nullable, maybe that’s why it went through). How does required array work?

Thanks!

[Gummibeer]

Hey,

the required part just works if you use the Builder ( https://github.com/fenos/Notifynder/blob/master/src/Notifynder/Builder/NotifynderBuilder.php ) - in the toArray() method it checks if it has all required fields.

After reading the code and so on I saw that we miss this part sorry 😕 😄
I will add a fix today that will allow you to set every wished custom key on the notification and returns an instance of the builder to allow chaining.

Except of this we are working on version4 for this package with a whole new codebase - most things are working (storing, retrieving, parsing, translating notifications) - if you have time we would be happy if you can test it and give some feedback!?

[Gummibeer]

The last push was for version4 to fix this issue. It isn't fixed in the current stable 3.2 version.

For version 4 I've added the way how to set these fields in the new docu: http://notifynder.info/Version_4/Usage/Send_Notifications