Form widget and GlobalKey in Flutter - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

What happens when you call validate() on a Form with a GlobalKey?

Consider a Flutter app with a Form widget linked to a GlobalKey. What is the result of calling _formKey.currentState!.validate()?

Flutter

final GlobalKey<FormState> _formKey = GlobalKey<FormState>();

Form(
  key: _formKey,
  child: TextFormField(
    validator: (value) => value!.isEmpty ? 'Empty!' : null,
  ),
);

// Later in code
bool isValid = _formKey.currentState!.validate();

A It submits the form data to the server automatically.

B It resets all form fields to empty values.

C It throws an error because validate() is not a method of FormState.

D It runs all validators in the form fields and returns true if all are valid.

💡 Hint

Think about what validate() does in a form context.

Calling validate() on the FormState runs all validators of the form fields and returns true only if all validators return null (meaning valid). It does not reset or submit the form.

❓ lifecycle

intermediate

What is the role of GlobalKey in managing Form state?

Why do we use a GlobalKey with a Form widget in Flutter?

A To uniquely identify the Form widget and access its state from anywhere in the widget tree.

B To style the Form widget with global colors.

C To automatically save form data to local storage.

D To prevent the Form widget from rebuilding.

💡 Hint

Think about how you access form methods like validate() or save().

GlobalKey allows you to access the FormState object, which holds the current state of the Form, enabling you to call methods like validate() or save() from outside the Form widget.

📝 Syntax

advanced

Which code snippet correctly uses GlobalKey to validate a Form?

Select the code snippet that correctly creates a GlobalKey, assigns it to a Form, and validates the form on button press.

A

final _formKey = GlobalKey();

Form(
  key: _formKey,
  child: TextFormField(validator: (v) => v!.isEmpty ? 'Empty' : null),
);

ElevatedButton(onPressed: () {
  if (_formKey.currentState.validate()) {
    print('Valid');
  }
}, child: Text('Check'))

B

final _formKey = GlobalKey<FormState>();

Form(
  key: _formKey,
  child: TextFormField(validator: (v) => v!.isEmpty ? 'Empty' : null),
);

ElevatedButton(onPressed: () {
  if (_formKey.currentState!.save()) {
    print('Valid');
  }
}, child: Text('Check'))

C

final _formKey = GlobalKey<FormState>();

Form(
  key: _formKey,
  child: TextFormField(validator: (v) => v!.isEmpty ? 'Empty' : null),
);

ElevatedButton(onPressed: () {
  if (_formKey.currentState!.validate()) {
    print('Valid');
  }
}, child: Text('Check'))

D

final _formKey = GlobalKey<FormState>();

Form(
  key: _formKey,
  child: TextFormField(validator: (v) => v!.isEmpty ? 'Empty' : null),
);

ElevatedButton(onPressed: () {
  if (_formKey.validate()) {
    print('Valid');
  }
}, child: Text('Check'))

💡 Hint

Remember how to access FormState and call validate().

Option C correctly declares GlobalKey, assigns it to the Form's key, and calls validate() on currentState. Other options have errors like missing type, wrong method calls, or missing null safety operators.

🔧 Debug

advanced

Why does _formKey.currentState return null sometimes?

In a Flutter app, you get a null error when calling _formKey.currentState!.validate(). What is the most likely cause?

A The GlobalKey was declared as final instead of var.

B The Form widget is not mounted in the widget tree when validate() is called.

C The validator function returns null instead of a string.

D The TextFormField is missing a controller.

💡 Hint

Think about widget lifecycle and when currentState is available.

currentState is null if the Form widget is not yet inserted in the widget tree or has been removed. Calling validate() too early causes null errors.

🧠 Conceptual

expert

How does GlobalKey help preserve Form state during widget rebuilds?

In Flutter, why does using a GlobalKey help keep the form field values and validation state intact when the widget tree rebuilds?

A GlobalKey uniquely identifies the Form widget, so Flutter reuses the existing state instead of creating a new one.

B GlobalKey automatically saves form data to disk and restores it after rebuilds.

C GlobalKey disables widget rebuilds for the Form and its children.

D GlobalKey forces the Form to rebuild from scratch every time.

💡 Hint

Think about how Flutter matches widgets and their states.

GlobalKey lets Flutter know which widget instance corresponds to which state object, so during rebuilds, the state is preserved and reused rather than reset.