这是indexloc提供的服务,不要输入任何密码
Skip to content

Fix Typos in MetaGenerator.js Documentation Comments #3993

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 13, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions server/utils/boot/MetaGenerator.js
Original file line number Diff line number Diff line change
Expand Up @@ -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 {
Expand Down