wackbyte d9b3849454 Fix inconsistent naming of OAuth 2.0 ENABLE setting (#28951) ... Renames it to `ENABLED` to be consistent with other settings and deprecates it. I believe this change is necessary because other setting groups such as `attachment`, `cors`, `mailer`, etc. have an `ENABLED` setting, but `oauth2` is the only one with an `ENABLE` setting, which could cause confusion for users. This is no longer a breaking change because `ENABLE` has been set as deprecated and as an alias to `ENABLED`.		2024-01-28 12:36:44 +00:00
..
config
actions_test.go
actions.go
admin.go
api.go
asset_dynamic.go
asset_static.go
attachment_test.go
attachment.go
cache.go
camo.go
config_env_test.go
config_env.go
config_provider_test.go
config_provider.go
config.go
cors.go
cron_test.go
cron.go
database_sqlite.go
database_test.go
database.go
federation.go
git_test.go
git.go
highlight.go
i18n.go
incoming_email.go
indexer_test.go
indexer.go
lfs_test.go
lfs.go
log_test.go
log.go
mailer_test.go
mailer.go
markup.go
metrics.go
migrations.go
mime_type_map.go
mirror.go
oauth2.go	Fix inconsistent naming of OAuth 2.0 ENABLE setting (#28951)	2024-01-28 12:36:44 +00:00
other.go
packages_test.go
packages.go
path_test.go
path.go
picture.go
project.go
proxy.go
queue.go
repository_archive_test.go
repository_archive.go
repository.go
security.go
server.go
service_test.go
service.go
session.go
setting_test.go
setting.go
ssh.go
storage_test.go
storage.go
task.go
time.go
ui.go
webhook.go