Ask AI
Skip to main content

Don't reload template

Function: Don't reload template​

This action is used when you want to prevent the current page or template from automatically refreshing after another action has completed. Normally, after certain operations (like saving data or submitting a form), your application might automatically reload the current view to show the latest information. This action gives you control, allowing you to keep the current template displayed without a full refresh, which can lead to a smoother user experience.

Input​

This action does not require any specific inputs. It simply performs its function when triggered.

Output​

This action does not produce any direct output values. Its effect is on the application's behavior (preventing a template reload).

Execution Flow​

Real-Life Examples​

Example 1: Saving a User Preference without Page Refresh

  • Scenario: A user changes a theme preference (e.g., "Dark Mode") on a settings page. The change is saved to the database, but you want the user to remain on the settings page without it flickering or reloading.
  • Inputs: None.
  • Result: The theme preference is saved, and the settings page remains exactly as it was, without reloading. The user can continue making other changes or navigate away smoothly.

Example 2: Submitting a Quick Comment on a Blog Post

  • Scenario: On a blog post page, a user submits a new comment. The comment is added to the database, and perhaps appears instantly below the post, but you don't want the entire blog post page to reload, which could interrupt the user's reading.
  • Inputs: None.
  • Result: The comment is successfully submitted and displayed (if your application updates the UI dynamically), and the blog post page stays open and active without a full refresh.

Example 3: Updating a Shopping Cart Item Quantity

  • Scenario: A user is viewing their shopping cart and changes the quantity of an item. The system updates the quantity and recalculates the subtotal for that item. You want this update to happen seamlessly without reloading the entire shopping cart page.
  • Inputs: None.
  • Result: The item quantity is updated in the cart, the subtotal is recalculated, and the shopping cart page remains open and responsive, providing a fluid experience.