lion-packages/bundle

lion-framework configuration and initialization package

bundle's Issues

User permissions error at project level

It has been detected when cloning the project or installing it that some parts generated directly from the container come out with SU permissions, this prevents modifying/deleting files since it always requests SU user authorization to be able to manipulate some sections of the project.

The vendor is protected and some files that could have been generated, is it possible to make some configuration that allows all actions to be with permissions for the user of my machine and not the SU user?

Problem detected in "Debian 12" with "Docker"

Improvements for response functions

The internal helpers of the framework have 4 response functions based on objects (success/error/warning/info) these functions have 3 parameters for defining a response.

It has been necessary to modify the original operation of the functions for their parameterization. The functions have their parameters defined as follows:

• int $code
• mixed $response
• mixed $data

It is necessary to modify their order to create response objects more easily, you must organize the parameters as follows:

• mixed $response
• int $code
• mixed $data

New helper support for custom responses

Is it possible to add a new response function "response"? this allows custom responses

response('my_custom_response', ''my_message", 500);

This allows us to return our own answers based on a certain specification.

Library support and integration

It is necessary to carry out the necessary refactoring to convert the package to a library since it needs to be installed in the framework as a plugin package.

Refactor:

• Commands
• Traits
• predis/predis package integration
• lion/command package integration
• lion/test package integration

This will allow it to be installed in the framework as a library and thus remove the packages stored in the framework.

Generation of invalid configuration file

It has been found that when generating a FrontEnd Web project with vite, a config/resources.php file is generated.
This is wrong since the vite project configuration is added in config/vite.php, when the file is required to be deleted it is not allowed due to user permissions which is defined as 'root' which prevents removing that file.