thats like trying to invoke an express function inside of an express function
Why not call 1 netlify function and call normal functions in it?
and those normal functions can chain
The only "netlify function" part that is strict is the execution environment and the exposed function you pass to
exports.handler. Pass that just create other JS functions to call inside of that function, which should give what you want
const fetchAllProducts = async () => {
const categories = await GetActiveCategories();
const categoriesIdArray = categories.map(category => category.CategoryId);
const productsNested = await Promise.all(categoriesIdArray.map(categoryID => getSearchResults(' ', categoryID)));
return ProductsNested.flat()
}
const hotDeals = async () => {
const products = await fetchAllProducts();
return products.filter(product => product.DiscountPercentage > 15)
}my lambda is to implement this functionality, the idea is to have one lambda that does a fetch of active categories, and then the next lambda get this data to calls the getSearchResults lambda to return a list of all products.
since we write normal javascript in a way that has seperate functions for each specific task, in a lambda are we supposed to not follow that pattern and write a big function that does everything in it?
to leverage lambda/cloud functions you just need to provide 1 function "publically" so netlify can call it, and pass in the arguments, past that it usually doesn't care except that you "respond" somehow. Just like express you can write whatever you want within the handler, how-ever you want to handle it
@brad sorry i didn't understand that, this is what i tried doing
import fetch from 'node-fetch';
const {API_TOKEN} = process.env;
exports.handler = async (event,context,callback) => {
const activeCategories = await fetch('/.netlify/functions/getActiveCategories')
const categoriesIdArray = categories.map(category => category.CategoryId);
const productsNested = await Promise.all(categoriesIdArray.map(categoryID => getSearchResults(' ', categoryID)));
callback(null,{
statusCode: 200,
body: JSON.stringify(const productsNested)
})
}
I also tried doing
import getActiveCategories from './getActiveCategories';
and then
const activeCategories = await getActiveCategories()
Oh your trying to make an http request to another function
you need to call it using
fetch as if your calling it from the front-end. Or seperate out the logic in the getActiveCateogires to an actual function and cal it like your last example
but that only works if the server knows what function your talking about
import fetch from 'node-fetch';
const {API_TOKEN} = process.env;
exports.handler = async (event,context,callback) => {
const activeCategoriesRes = await fetch('https://api.example.com/category/GetActiveCategories',{
method: 'GET',
headers: {'APIToken': API_TOKEN}
});
const activeCategoriesData = await activeCategoriesRes.json();
const categories = activeCategoriesData.result;
const categoriesIdArray = categories.map(category => category.CategoryId);
const productsNested = await Promise.all(categoriesIdArray.map(categoryID => {
const categoryProductsRes = await fetch(`http://api.example.com/Product/GetProductSearchByCategory`,{
method: 'POST',
headers: {
'Content-Type': 'application/json',
'Accept': 'application/json',
'APIToken': API_TOKEN
},
body: JSON.stringify({
"CategoryID": CategoryID,
"Search": " ",
"lstBrand": [],
"lstColor": [],
"lstSize": [],
"PriceFrom": 0,
"PriceTo": 0,
"MaxPrice": 0,
"Page": 1,
"Show": 9999,
"UserID": ""
})
})
const categoryProductsData = await categoryProductsRes.json();
return categoryProductsData.result;
}));
const productsList = productsNested.flat();
const hotDeals = productsList.filter(product => product.DiscountPercentage > 15 && product.SellingPrice > 50);
callback(null,{
statusCode: 200,
body: JSON.stringify(hotDeals)
})
}
otherwise you will have to call the function using fetch correctly
I'd recommend reading into both approaches. The sharing code approach is more complex in terms of setting up, but will be more performant and scalable for development
I don't suggest believing you need any more guidance than that most of the time. If you don't know what concepts i'm talking about then it sounds like its time to first figure out what I'm talking about (by getting more familiar in any way possible) and then learn how you can apply it in your own project
Same goes for your errors. I'm sure you will figure it out after some time, but don't expect to be able to run code, figure stuff out without trouble, that isn't the point. The point is being presented a problem and being able to figure it out over time. Google your way out of your error, bash your head against the code, and learn through trial error and understanding. That is how you get experience
that it periodically fetches data from the original server, say once every 2 hours and then caches it
The netlify server instance shouldn't stay running longer than a few seconds, or minutes after each call between calls. Thus you will need something running "long term" if you want to cache it for 2 hours
Hello Fellow Campers. I am looking for FE Campers to join a project on which I am working on. I recently participated in a hackathon and WON in it. Now I am being requested to develop it further and superfast. Will be glad to get any of the Fellow Campers to test out the skills that we have acquired through FCC onto a real life product. Here is a link to the blog post mentioning about my team wining the hackathon https://blog.kyber.network/kyberdefi-hackathon-meet-the-winners-bea5bc9ec983 . Drop me a dm if you would like to come work on this.
Anybody knows how I can solve this issue?