Contrib.social

Establish naming convention for form IDs

Open on Drupal.org →
Created on 21 May 2009, almost 16 years ago
Updated 10 March 2025, about 2 months ago

Proposal: Establish a naming convention (and/or enforce one, but that probably won't be so popular...) so that all form definition functions in core are whatever_form(). This would make all validate/submit functions are whatever_form_validate/submit() and all form theme functions theme_whatever_form().

Pros:
a) Makes it easy to tell at a glance what functions are related to forms and belong together.
b) No more searching API functions and coming across something like system_modules() and thinking it does something entirely different from what it actually does.
c) Consistency!

Cons:
Absolutely none! ;) Unless someone has any objections. :)

📌 Task
Status

Postponed: needs info

Version

11.0 🔥

Component

forms system

Created by

🇨🇦Canada webchick Vancouver 🇨🇦

Live updates comments and jobs are added and updated live.
  • DrupalWTF

    Worse Than Failure. Approximates the unpleasant remark made by Drupal developers when they first encounter a particular (mis)feature.

  • API clean-up

    Refactors an existing API or subsystem for consistency, performance, modularization, flexibility, third-party integration, etc. May imply an API change. Frequently used during the Code Slush phase of the release cycle.

  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Comment about 2 months ago →
    🇺🇸United States smustgrave

    Thank you for creating this issue to improve Drupal.

    We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024