#jean-baptiste-r_code

1 messages · Page 1 of 1 (latest)

jade knollBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1349745838586597408

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

raw ocean
#

Hey !
Well, the problem is fixed. Hot reload didn't work ... 😓

I just have a little question about the code: what is the "future_requirements: 'include'" property please ?

#

Oh and another question: What is the difference between eventually_due and currently_due ?
I'd like to generate a link to update every information, I don't get why this could be necessary

jade knollBOT
neon dagger
#

Hey there

#

So some verification requirements are triggered on thresholds based on time/processing volume.

#

So if you want to request everything up front then you use collection_options.fields: 'eventually_due'.

#

As well as future_requirements: 'include' to really take care of everything possible.

raw ocean
#

Okay nice !
Thank you 🙂
Have a good day