Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Document Element::isFieldEmpty usage

Open
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
documentation

Research direction

Search the documentation for Element::isFieldEmpty and entry.isFieldEmpty('myField'), then review how required validation is described. Done means the docs explain that this is a valid way to check whether a field is empty regardless of fieldtype, including the usage context described in the issue.

Written by the indexing model from the issue text.

Description

Started: https://github.com/craftcms/cms/issues/5300

I would like to see isFieldEmpty (Element::isFieldEmpty, entry.isFieldEmpty('myField'), et. al.) documented as a valid way to check a field for empty regardless of the fieldtype.

It looks like Craft uses this internally for required validation, but can be useful in other contexts as well.

In my use-case, I'm mapping a set of element fields, but don't care about the actual field output data, only if it has any.

Seems like the right thing to use, but I'm wary of relying on it without anything in the docs.

Dominant language
JavaScript
Stars
42
Forks
160
Avg merge
3h 9m
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from craftcms/docs

All issues in craftcms/docs

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.