michael/merlyn
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix Typos in MetaGenerator.js Documentation Comments (#3993)

Browse Source 
Update MetaGenerator.js

Co-authored-by: Timothy Carambat <rambat1010@gmail.com>
This commit is contained in:
fuder.eth 2025-06-13 18:56:40 +03:00 committed by GitHub
parent 825c5b044e
commit 3c89ea987f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
server/utils/boot/MetaGenerator.js
View File

@ -12,9 +12,9 @@
* Since we are an SPA, we can just render the primary page and the known entrypoints for the index.{js,css}
* we can always start at the right place and dynamically load in lazy-loaded as we typically normally would
* and we dont have any of the overhead that would normally come with having the rewrite the whole app in next or something.
* Lastly, this class is singleton, so once instantiate the same refernce is shared for as long as the server is alive.
* Lastly, this class is singleton, so once instantiate the same reference is shared for as long as the server is alive.
* the main function is `.generate()` which will return the index HTML. These settings are stored in the #customConfig
* static property and will not be reloaded until the page is loaded AND #customConfig is explicity null. So anytime a setting
* static property and will not be reloaded until the page is loaded AND #customConfig is explicitly null. So anytime a setting
* for meta-props is updated you should get this singleton class and call `.clearConfig` so the next page load will show the new props.
*/
class MetaGenerator {