laravel-enso / documentation Goto Github PK

Starting point: laravel-enso/helpers#10 (comment)

You should add local enums to a LocalStateBuilder and reuse the bootEnums helper available in the FE.

The you can do

computed: {
   ...mapState('local', ['enums']),
}

....

$this.enums.myEnum._get(key)`

usage example

full api

In regards to :

https://docs.laravel-enso.com/guide/development.html#changing-back-end-logic

If the modifications you require are more extensive and cannot be resolved via using dependency injection, the other option is to overwrite the required routes, and point to your local implementation/controllers.

Can you give me an example of using dependency injection ? I'm trying to piece together this scenario where I need to extend your "permissions", let's say, by having another related entity to it, therefore I need your permissions to have a "belongsToMany".

I'm also considering using tentacles (https://github.com/greabock/tentacles) on all Models...

PS: based on your answer I'll add also to the documentation everything that may be helpful.

Hello i have a problem to edit field. I have an error, if i set the field to editable the systemshow me an error "type fild is not valid"

How can i resolve this issue?

dateFormat, string, sets the default date format for datepicker fields. Note that for this fields and instance of Carbon is expected

Under Form Builder's Global config, when trying to pass a Carbon instance to a datepicker (using $this->form->value( in ModelForm's create() it results in an [Object] Object being displayed, instead of a date.

What's the expected way to pass a default date to it? (taking localisation into account)

I tried on a fresh new server a new installation of laravel-enso just to give a look on how it behaves and how it globally works.
I quite like the demo and functionalities that it promises, unfortunately no matter what I did, installation just doesn't work.
I keep getting "ErrorException -> Failed to open stream: No such file or directory" because of some wrong caching references.
I tried also to clear all Laravel's cache but nothing was really useful.
Hope that authors will review in a better and clear way the full process.

https://docs.laravel-enso.com/backend/history-tracker.html is not discoverable in the back-end menu, it is via search though, some meta missing somewhere? or random error somehow?

Hi,
Section "getting-started / Installation Steps" missing the step for :
php artisan vendor:publish --all
Without the web app does not work, isn't it ?
Cheers

• currencies
• enums
• dynamic-methods
• pdf
• products
• services
• versions
• emails
• excel

Also, besides docs we need:

• reamde,
• style-ci & codacy integrations,
• badges

Hi, just wanted to know if we could easily use this library without laravel, with a custom backend ?

Hi,

I'm reading this: https://docs.laravel-enso.com/guide/under-the-hood.html#usergroups-roles-users

• users represent the operators using the application
• roles are collections of permissions
• user groups (previously owners) can represent departments, types, and even companies
• an user group can have many users
• an user group can have many roles
• an user has just one user group and just one role
• the role of a user may only be one of the roles available for its user group
• users have an active or inactive status, where inactive users cannot login or make requests in the application (but can set/reset their password)
• the Role model contains the AdminId and SupervisorId constants that determine who the administrator and supervisor roles are
• the UserGroup model contains the AdminGroupId constant that is used to determine which is the Administrator user group

and I understand each point independently, but all together I'm missing the global purpose and why were those things implemented this way.

What is the purpose of having a user linked to a UserGroup/Role pair, if in the end it's the role sets of permissions that matters. Why have the UserGroup in the first place?

Is is just for pure classification so that you have different, let's say... companies permissions under the same usergroup?

I'm trying to investigate the possibility to expand this functionality to multiple sets of permissions per user. Let's say if a user works for 2 companies, and it has 2 different roles in each company, I wouldn't like to create 2 users for the same person, therefore, I'm thinking to give multiple roles to the same user. This scenario will generate permission conflicts, but a simple rule as "the highest permission wins" will work for me (if one role has "read only" and another has "read/write" - the global merged permission will be "read/write"). And I'm not sure if maybe I can work with what is already implemented, and I'm missing some things, or, I was not intended this way, and I have to implement this solution.

Thank you.

https://docs.laravel-enso.com/guide/getting-started.html#installation-steps still shows the old installation steps (cleared my cache)

In regards to :

When we must make breaking changes to the packages, we increase the minor version. Due to how dependencies are defined, composer will not update the dependencies for you in that case, that's why you need to look at the changelog, be aware of the changes, update your code and then manually update the dependencies' minor version, so that you can continue to receive updates.

https://docs.laravel-enso.com/guide/usage.html#updates

I just want to clarify one thing:
If I run composer update it will not update laravel-enso\enso + all other enso dependncies like laravel-enso\table, laravel-enso\select, laravel-enso\data-export etc..?

By

update your code
you mean I need to manually merge all changes from current changelog into my local vendor\laravel-enso ...?

Or all enso related changes are merged but only version is not updated?

manually update the dependencies' minor version

This is confusing for me because on composer update I see some things getting updates from laravel-enso, but version remains the local one...

Example:
https://docs.laravel-enso.com/packages/role-manager.html
https://docs.laravel-enso.com/packages/vue-datatable.html#features

At first glance this is an oversight in vuepress' upgrade guide, as the service worker setting now defaults to false.
It looks like the manifest,json was provided outside of the repo (perhaps by netlify?)

Either way, it's currently not there anymore meaning that anyone who ever visited the docs site will keep getting the old docs served from the local cache (even after a force refresh; on subsequent visits; as the service worker takes over next time again)

(I'd provide a PR if I had more experience with VuePress & the config used, sadly that's not the case)