fix: replace .Site.IsMultiLingual with hugo.IsMultilingual #886
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The change from
.Site.IsMultiLingualtohugo.IsMultilingualwas made to ensure compatibility with newer versions of Hugo. The method.Site.IsMultiLingualwas deprecated starting from Hugov0.124.0,and it was officially removed in v0.140.0. As part of Hugo's ongoing effort to improve the platform, it is essential to update code to use the recommended alternatives before older methods are fully phased out.hugo.IsMultilingual is the new, recommended approach to check if the site is multilingual, aligning with Hugo's updated API. This change helps future-proof the site and ensures it continues to function correctly with the latest Hugo versions. By adopting this change, we also avoid potential build issues when upgrading Hugo in the future.