github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 14:21:55 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #1700] Make "image" field optional #26196

New Issue
Closed
opened 2026-04-17 16:40:37 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-17 16:40:37 -05:00
Owner
Copy Link

Originally created by @zispidd on GitHub (Mar 5, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/1700

I have a project that does not use user images. I want to try your library, but I don't want to clutter my schema with an unnecessary field that is not and will not be used. Do you plan this kind of customization?

Originally created by @zispidd on GitHub (Mar 5, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/1700 I have a project that does not use user images. I want to try your library, but I don't want to clutter my schema with an unnecessary field that is not and will not be used. Do you plan this kind of customization?
GiteaMirror added the locked label 2026-04-17 16:40:37 -05:00
GiteaMirror commented 2026-04-17 16:40:39 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Mar 5, 2025):

Yes. We're working towards making the user schema more modular and fully user definable.

<!-- gh-comment-id:2702165572 --> @Bekacru commented on GitHub (Mar 5, 2025): Yes. We're working towards making the user schema more modular and fully user definable.
GiteaMirror commented 2026-04-17 16:40:39 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Jun 14, 2025):

Hi, @zispidd. I'm Dosu, and I'm helping the better-auth team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • You requested the ability to make the "image" field optional in the library's schema.
  • @Bekacru confirmed that the team is working on making the user schema more modular and user-definable.
  • The response received positive reactions, showing community interest and support.

Next Steps:

  • Please let us know if this issue is still relevant to the latest version of the better-auth repository by commenting here.
  • If there is no further activity, this issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!

<!-- gh-comment-id:2972848007 --> @dosubot[bot] commented on GitHub (Jun 14, 2025): Hi, @zispidd. I'm [Dosu](https://dosu.dev), and I'm helping the better-auth team manage their backlog. I'm marking this issue as stale. **Issue Summary:** - You requested the ability to make the "image" field optional in the library's schema. - @Bekacru confirmed that the team is working on making the user schema more modular and user-definable. - The response received positive reactions, showing community interest and support. **Next Steps:** - Please let us know if this issue is still relevant to the latest version of the better-auth repository by commenting here. - If there is no further activity, this issue will be automatically closed in 7 days. Thank you for your understanding and contribution!
GiteaMirror commented 2026-04-17 16:40:39 -05:00
Author
Owner
Copy Link

@zispidd commented on GitHub (Jun 14, 2025):

still relevant

<!-- gh-comment-id:2972865464 --> @zispidd commented on GitHub (Jun 14, 2025): still relevant
GiteaMirror commented 2026-04-17 16:40:40 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Sep 13, 2025):

Hi, @zispidd. I'm Dosu, and I'm helping the better-auth team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested making the "image" field optional in the user schema to reduce unused fields.
  • The team is working on a more modular and fully user-definable user schema.
  • The community responded positively to this planned improvement.
  • You confirmed the issue remains relevant.
  • The issue is currently unresolved.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of better-auth by commenting here.
  • If I do not hear back within 7 days, the issue will be automatically closed.

Thank you for your understanding and contribution!

<!-- gh-comment-id:3288576103 --> @dosubot[bot] commented on GitHub (Sep 13, 2025): Hi, @zispidd. I'm [Dosu](https://dosu.dev), and I'm helping the better-auth team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested making the "image" field optional in the user schema to reduce unused fields. - The team is working on a more modular and fully user-definable user schema. - The community responded positively to this planned improvement. - You confirmed the issue remains relevant. - The issue is currently unresolved. **Next Steps:** - Please let me know if this issue is still relevant to the latest version of better-auth by commenting here. - If I do not hear back within 7 days, the issue will be automatically closed. Thank you for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label locked
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#26196
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?