Form widget and GlobalKey in Flutter - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the Form widget in Flutter?

The Form widget groups multiple form fields together and helps manage their validation and saving as a single unit.

beginner

What is a GlobalKey used for in Flutter forms?

A GlobalKey uniquely identifies the FormState so you can access and control the form (like validating or saving) from outside the form widget.

intermediate

How do you validate all fields inside a Flutter Form?

Call _formKey.currentState!.validate() where _formKey is the GlobalKey<FormState>. It runs all validators and returns true if all pass.

intermediate

Why should you use a GlobalKey<FormState> instead of a local key for a form?

Because GlobalKey allows you to access the form's state from anywhere in the widget tree, enabling actions like validation and saving outside the form widget.

intermediate

What happens if you call _formKey.currentState!.save() in Flutter?

It triggers the onSaved callbacks of all form fields inside the form, allowing you to store or process the input values.

What type should a GlobalKey have to manage a Flutter form?

A GlobalKey<FormState>

B GlobalKey<StatefulWidget>

C GlobalKey<Form>

D GlobalKey<Widget>

The GlobalKey must be typed as GlobalKey<FormState> to access the form's state methods like validate() and save().

Which method validates all fields inside a Flutter form?

A validate() on GlobalKey

B check() on Form widget

C validate() on FormState

D checkFields() on FormState

Calling validate() on the FormState runs all field validators and returns true if all are valid.

How do you access the form state from outside the form widget?

A Using a local key

B Using a StatefulWidget

C Using a BuildContext only

D Using a GlobalKey<FormState>

A GlobalKey<FormState> allows you to access the form state anywhere, unlike local keys or BuildContext.

What does the onSaved callback do in a form field?

A Validates the field input

B Saves the field value when <code>save()</code> is called on the form

C Resets the field value

D Displays an error message

onSaved is called during FormState.save() to store or process the input value.

What will _formKey.currentState!.validate() return if any field is invalid?

A false

B true

C null

D throws an error

If any validator returns false, validate() returns false indicating the form is not valid.

Explain how to use a Form widget with a GlobalKey to validate user input in Flutter.

Think about how you connect the key to the form and trigger validation.

Describe the role of onSaved callbacks in Flutter forms and how they work with GlobalKey.

Consider when and how the form fields save their data.

Practice

1. What is the main purpose of using a Form widget in Flutter?

easy

A. To group multiple input fields for validation and saving

B. To create a button that submits data

C. To display images in a grid layout

D. To manage app navigation between screens

Solution

1. Step 1: Understand the role of Form widget

   The Form widget groups input fields so you can validate and save them together.

2. Step 2: Compare options with Form's purpose

   Only To group multiple input fields for validation and saving describes grouping input fields for validation and saving, which is the Form's main use.

3. Final Answer:

   To group multiple input fields for validation and saving -> Option A

4. Quick Check:

   Form groups inputs = D [OK]

Hint: Form groups inputs for validation and saving [OK]

Common Mistakes:

• Thinking Form is for navigation or layout
• Confusing Form with buttons or images
• Assuming Form manages app state globally

2. Which of the following is the correct way to declare a GlobalKey for a Form in Flutter?

easy

A. final _formKey = GlobalKey();

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

C. final _formKey = GlobalKey<Form>();

D. final _formKey = GlobalKey<State>();

Solution

1. Step 1: Identify correct GlobalKey type for Form

   The GlobalKey must be typed as GlobalKey<FormState> to access the Form's state.

2. Step 2: Check each option's type

   final _formKey = GlobalKey<FormState>(); uses GlobalKey<FormState>(), which is correct. Others use wrong or incomplete types.

3. Final Answer:

   final _formKey = GlobalKey<FormState>(); -> Option B

4. Quick Check:

   GlobalKey typed as FormState = A [OK]

Hint: GlobalKey must be typed as GlobalKey<FormState>() [OK]

Common Mistakes:

• Using GlobalKey without type parameter
• Using GlobalKey<Form> instead of FormState
• Using GlobalKey<State> which is too generic

3. Given this Flutter code snippet:

final _formKey = GlobalKey<FormState>();

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

// Later in code
if (_formKey.currentState!.validate()) {
  print('Valid input');
} else {
  print('Invalid input');
}

What will be printed if the TextFormField is empty when validate() is called?

medium

A. Valid input

B. No output, code throws error

C. Invalid input

D. Nothing happens, validate() returns null

Solution

1. Step 1: Understand validator behavior

   The validator returns 'Enter text' if the field is empty, which means validation fails.

2. Step 2: Check validate() result

   validate() returns false if any validator returns a non-null string, so the else branch runs.

3. Final Answer:

   Invalid input -> Option C

4. Quick Check:

   Empty input triggers validator error = B [OK]

Hint: Validator returns error string means validate() is false [OK]

Common Mistakes:

• Assuming validate() returns true on empty input
• Confusing validator return null with error
• Thinking validate() throws error on empty input

4. Identify the error in this Flutter code snippet:

final _formKey = GlobalKey<FormState>();

Form(
  key: _formKey,
  child: TextFormField(
    validator: (value) {
      if (value!.length < 3) return 'Too short';
      return null;
    },
  ),
);

// Later
if (_formKey.currentState.validate()) {
  print('Valid');
}

medium

A. GlobalKey should be GlobalKey<Form>

B. Validator should return a boolean, not a string

C. Missing exclamation mark after currentState

D. Calling validate() without null check on currentState

Solution

1. Step 1: Check usage of currentState

   currentState can be null if Form is not mounted, so calling validate() without null check risks error.

2. Step 2: Review code for null safety

   The code calls _formKey.currentState.validate() without ! or ?. which causes a compile error in null-safe Dart.

3. Final Answer:

   Calling validate() without null check on currentState -> Option D

4. Quick Check:

   currentState may be null, needs ! or ? = A [OK]

Hint: Always null-check currentState before validate() [OK]

Common Mistakes:

• Forgetting to add ! after currentState
• Returning boolean from validator instead of string/null
• Using wrong GlobalKey type

5. You want to create a form with two TextFormFields and a submit button. You want to validate both fields and show errors if empty. Which approach correctly uses GlobalKey and Form to achieve this?

hard

A. Declare a GlobalKey<FormState>, assign it to Form's key, use validators on fields, call _formKey.currentState!.validate() on submit

B. Use separate GlobalKeys for each TextFormField and call validate() on each key

C. Use a GlobalKey without type parameter and call validate() on it

D. Wrap each TextFormField in its own Form widget with separate GlobalKeys

Solution

1. Step 1: Understand Form and GlobalKey usage

   One GlobalKey<FormState> is used to manage the whole Form and validate all fields together.

2. Step 2: Evaluate options for best practice

   Declare a GlobalKey<FormState>, assign it to Form's key, use validators on fields, call _formKey.currentState!.validate() on submit correctly uses one GlobalKey<FormState>, assigns it to Form, uses validators, and calls validate() once.

3. Final Answer:

   Declare a GlobalKey<FormState>, assign it to Form's key, use validators on fields, call _formKey.currentState!.validate() on submit -> Option A

4. Quick Check:

   Single GlobalKey<FormState> for whole Form = C [OK]

Hint: Use one GlobalKey<FormState> for entire Form [OK]

Common Mistakes:

• Using multiple GlobalKeys for each field
• Not typing GlobalKey as FormState
• Wrapping each field in separate Form widgets