Low-Code beginner's guide to optimising your data calls in a to-do list app with Noodl
Вставка
- Опубліковано 23 лип 2024
- Written guide to follow along: tinyurl.com/hkrn52m7
In this tutorial, I'll show you how to optimise your app so that it's doing the least calls to your back end as possible, using the Array node in Noodl to store and manipulate data in the front end browser session storage. That may sound scary, but don't worry! Noodl provides all the nodes we need to get this done without writing a single line of code (not that coding's a bad thing, just saying... 😏).
If you missed my guide on setting up a local, free copy of the Noodl back end, it's here: • How to set up your fir...
Don't forget to download the step by step instructions, you know, for those of us who still read sometimes: tinyurl.com/hkrn52m7
Contents
00:00 Introduction and pre-ramble
10:30 Add an array
17:30 Synchronise adding to DB and local array
21:20 Synchronise deleting from DB and local array
24:09 Communicate changes to the header
32:26 Importing and exporting the Noodl way
38:53 Conclusion and pro tips - Наука та технологія
Great, this isn't just a technical guide for optimization, it's a valuable perspective for project development. Love it!
Thanks! I’m really glad you found it useful :)
Quality content!
Thanks! I hope it helped :)
Great tuto Rick! Very "clinical" as you rightfully say. And good conclusion, saving at once in the end would further the optimization.
However, since we can reasonably expect that the task app will have a few pages, when one comes back to the "header" home page, the query to the server will run again. How could we make sure the query runs only once, when the app "initializes"?
This is a very good point! Thanks for bringing it up. Often in this case i would put the query at the “App” level, instead of the “Page” level. This means it will only run on full page load, and not when “routing” the user between the different page components of the app.
@@simple-rick-tutorials Thanks for the advice! 😀
At 38:00 the Did Mount signal does not actually trigger the filter for some reason, it only gets triggered base don the component input, any idea why?
Filters will run spontaneously on page load only if nothing is hooked up to their "Filter" signal input. As soon as you hook something up to the Signal Input of a node, it will only run when that specific signal is fired, it won't run spontaneously on page load anymore. We'd need to hook the 'Did Mount' signal from the page element up to the 'Task Item Changed' input of the Header component, for example, to reconnect the page loading signal. Does that answer your question?
It does! love it! thanks rick!!@@simple-rick-tutorials