As you're building out a web application, you'll have to be very careful with what is being exposed in the browser. In this lesson, let me show you the issues of using exposeLocalsToBrowser() by inspecting the source code of our pages. To fix these problems, we'll go over two different solutions of sanitizing objects before we send it to the browser. Finally, let's also discuss the options that can be passed into exposeLocalsToBrowser such as keys.
Comments (1)
Allen Xu
4 years ago
Hi Brian,
I have a question. why I use MongoDB store my data , and after almost 24 hours later, they all gone .Is that have to pay ?
Allen Xu
4 years ago
By the way , I think I user heroku , mlab.
Brian Voong
4 years ago
Allen Xu
4 years ago
still that question.how to set migrate:safe config? And where to set migrate:safe?
thanks.
Allen Xu
4 years ago
and by the way ,is that only using heroku with mlab have that problem?if I use mangoDB Atlas dont have this problem?
Brian Voong
4 years ago
Allen Xu
4 years ago
ok. thanks buddy.I will try that
kmcginnis
2 years ago
Mine is still getting destroyed with Atlas... I tried "migrate:safe" and thought it was working, but I just had the issue come up again.
kmcginnis
2 years ago
Trying "migrate:safe" in the models.js instead of on each individual model of the Post and User, I'll let you know if it comes up again. Thanks!