laravel-enso/people

Person management dependency for Laravel Enso

People

Person management dependency for Laravel Enso.

This package works exclusively within the Enso ecosystem.

The front end assets that utilize this api are present in the ui package.

For live examples and demos, you may visit laravel-enso.com

^{click on the photo to view a large size screenshot}

Installation, Configuration & Usage

Be sure to check out the full documentation for this package available at docs.laravel-enso.com

Contributions

are welcome. Pull requests are great, but issues are good too.

License

This package is released under the MIT license.

people's Issues

self::creating expects a person entry to already be present

As requested in #1, recreating

This is a bug.

Prerequisites

• Are you running the latest version?
• Are you reporting to the correct repository?
  (enso is made of many specialized packages: https://github.com/laravel-enso)
• Did you check the documentation?
• Did you perform a cursory search?

Description

from the 11.12 CHANGELOG:

update user and owner seeders with the ones from laravel-enso/core if they are not customized already (optional)

self::creating in the IsPerson trait seems to do an update; thus expecting an entry to already be there.

If I keep my existing UserSeeder configuration, the following error occurs

Steps to Reproduce

1. migrate:fresh --seed with a pre-11.12 userseeder (except for modifying owner to group)

Expected behavior

Seeding to happen

Actual behavior

Call to member function update() on null

create a People import

to be able to mass import people for a new application

Spelling correction: Mandatary should be Mandatory

This is a remark.

Prerequisites
[x ] Are you running the latest version?
[ x] Are you reporting to the correct repository?

In vendor/laravel-enso/people/Person.php the correct spelling is "Mandatory" instead of "Mandatary".

Binding custom person form has errors and won't let me create or edit anymore after update

production.ERROR: Argument 1 passed to LaravelEnso\People\Http\Controllers\Create::__invoke() must be an instance of LaravelEnso\People\Forms\Builders\PersonForm, instance of App\Forms\Builders\PersonForm given {"userId":2,"exception":"[object] (TypeError(code: 0): Argument 1 passed to LaravelEnso\People\Http\Controllers\Create::__invoke() must be an instance of LaravelEnso\People\Forms\Builders\PersonForm, instance of App\Forms\Builders\PersonForm given at /home/genealogia/public_html/vendor/laravel-enso/people/src/Http/Controllers/Create.php:10)

I am binding and it worked before. The only difference is I'm trying to manually add multi tenancy code to the table builder and forms as overwriting the route didn't work for me, unless I did that wrong?

Publish does not generate configuration file

Publishing the files for configuration does not generate a configuration file. I am unsure what it is meant to look like. This is the only step I had an issue with on my project where I am modifying persons to make it suit genealogy purposes more.

I need the configuration file to specify a local form and table template file. Thank you.

add screenshots

Creating a new person causes an update on every key-press

This is a question.

Prerequisites
[x ] Are you running the latest version?
[ x] Are you reporting to the correct repository?
[ x] Did you check the documentation?
[ x] Did you perform a cursory search?

Description
When creating a new person, every key-press in the fields Name, Appellative, Phone Number, Birthday, Unique Identifier and Notes results in a record update including a toaster message.
Is this intended? Because it's less than user friendly in my opinion.

Steps to Reproduce
Create a new person, type in a unique email address, change either one of the fields mentioned above.

Expected behaviour
Update to be performed when a "Save" button is pressed.

Actual behaviour
Each key press generates an update, a toaster message and a progress bar.

Bindings for Validations

People no longer has an interface contract for implementing the bindings of the request.
(https://github.com/laravel-enso/people/tree/9afd2df78e543c388bae95b57d3044471104a007/src/app/Contracts)

Documentation still advises to

bind your local implementations to the package's ValidatePersonRequest in your local AppServiceProvider

$this->app->bind(
    ValidatesPersonRequest::class, MyValidatePersonRequest::class
);

Contracts have since been removed

What is the suggested best practice and would it be possible to update the documentation?

self::creating expects a person entry to already be present

Self-made relation... and this is the result

This is a bug.

Prerequisites

• Are you running the latest version?
• Are you reporting to the correct repository?
  (enso is made of many specialized packages: https://github.com/laravel-enso)
• Did you check the documentation?
• Did you perform a cursory search?

Description

from the 11.12 CHANGELOG:

update user and owner seeders with the ones from laravel-enso/core if they are not customized already (optional)

self::creating in the IsPerson trait seems to do an update; thus expecting an entry to already be there.

If I keep my existing UserSeeder configuration, the following error occurs

Steps to Reproduce

1. migrate:fresh --seed with a pre-11.12 userseeder (except for modifying owner to group)

Expected behavior

Seeding to happen

Actual behavior

Call to member function update() on null

Duplicate keys detected

I have the following situation:

• 2 users
• 1 person
• both users belong to the same physical person

If I open people table I get the error:
Duplicate keys detected
and 2 lines are shown

Query for people table should be grouped by people id.

Btw.: The user_id is shown in people table and not the person_id

Login - The device name field is required.

Hi,
I'm doing a clean install, following the instructions from https://github.com/laravel-enso/Enso

Everything goes fine, but I cannot log in (initial credentials [email protected]/password).

The response is
422 Unprocessable Entity
{"message":"The given data was invalid.","errors":{"device_name":["The device name field is required."]}}

Thank you!