Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: custom user model #324

Merged
merged 1 commit into from
Sep 1, 2024
Merged

feat: custom user model #324

merged 1 commit into from
Sep 1, 2024

Conversation

atmonshi
Copy link
Member

@atmonshi atmonshi commented Sep 1, 2024

No description provided.

@atmonshi atmonshi linked an issue Sep 1, 2024 that may be closed by this pull request
Copy link

what-the-diff bot commented Sep 1, 2024

PR Summary

  • Addition of 'User' Model to Various Files
    The 'User' model has been added to both the 'b/config/zeus-bolt.php' and 'docs/getting-started/configuration.md' files. This update helps in recognizing and utilizing the 'User' model across different areas of the application.

  • Refinement of Configuration File
    The Configuration.php file has been updated to return null when no model is detected within the array. This helps in preventing potential errors that may occur when there is no model found.

  • Consolidation of User Model Reference in Multiple Files
    The reference model for the user has been standardized across several files (ResponseExporter.php, ManageResponses.php, Collection.php, Form.php, Response.php). The system now initially looks for the 'User' model from the BoltPlugin. If it is not found, the system reverts to using the model defined under 'auth.providers.users.model' in the configuration. This change improves code consistency and maintainability while ensuring applications function correctly when the 'User' model from BoltPlugin is unavailable.

@atmonshi atmonshi merged commit 2309d6c into 3.x Sep 1, 2024
5 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Can I use other "users" table?
1 participant