forked from getzola/zola
-
Notifications
You must be signed in to change notification settings - Fork 0
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
[pull] master from getzola:master #140
Open
pull
wants to merge
97
commits into
psy-repos-rust:master
Choose a base branch
from
getzola:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
* chore: format themes file * feat: add aspect ratio to theme images
* refactor: pattern to separate file causes a lot of lag and also probably isn't the best to inline since we have scss preprocessing * fix: escape quotes properly * feat: improve header styles
Co-authored-by: GitHub Action <[email protected]>
* Add overflow wrap for long words * Fix specific case of overflowing text
Co-authored-by: GitHub Action <[email protected]>
* Match <!-- more --> without spaces * Add tests for new <!-- more --> handling, with a note on pulldown-cmark bug
This fixes a bug introduced in #2258 The issue arose when `output_path` was relative. The request being served would be canonicalized and this would be a string. So, for example, if you were serving content from `public` the code [right after](https://github.com/getzola/zola/blob/38199c125501e9ff0e700e96adaca72cc3f25d2b/src/cmd/serve.rs#L144-L147) the canonicalization checking if `root.starts_with(original_root)` would always return `false` since an absolute path, `/some/path/to/content` would never start with a string like `public`.
…27.0.0.1 (#2395) * Parse interface as IpAddr, allow IPv6. * Default base_url to socket address, instead of 127.0.0.1
* Remove ensure_directory_exists since it's identical to create_directory, and misleading * Don't create directories unless needed; rely on create_dir_all instead of manually iterating over components
* Allow ignoring files when link checking * cargo fmt * Fix tests * Remove mystery duplicate function..? * Add in some mysterious missing code..? * Simple tests for link checker file globs in config * cargo fmt * Remove comment * convert expect to error propagation * Address comments * cargo fmt
* adding optional `lang` arugment to `get_section` global function * Add handling of default language passed in `lang` argument of `get_section` * Remove clones for path. Change "?" to an explicit check for error * lint changes * Clean up error handling for add_lang_to_path call * fix format * Add optional parameter "lang" to get_page template function. Add check for language available in config. * Modify helper function name from calculate_path to get_path_with_lang. Modify documentation for get_section and get_page to include equivalent calls without using lang argument to demostrate how lang argument effects pathing.
#2432) The pulldown_cmark escaping functionality is now shipped in a separate pulldown_cmark_escape crate (https://crates.io/crates/pulldown-cmark-escape), starting with v0.10.0. The markdown.rs module has to be adapted to a few API changes in pulldown_cmark, and we have to introduce explicit handling of <img> alt text to ensure it continues to be properly escaped. There are also a few other behavior changes that are caught by the tests, but these actually seem to be desired, so I've updated the insta snapshot files for those tests to incorporate those changes. Specifically, one footnote-parsing case seems to be handled better now, and pulldown-cmark's `push_html` now doesn't escape quotes in text nodes anymore (see pulldown-cmark/pulldown-cmark#836).
…#2311) * Fix --base-url improper path and protocol handling. * Fix formatting.
Fixes passing section.transparency for #1840
* Fix resizing for images with EXIF orientation * Added test for asymmetric resize for exif images --------- Co-authored-by: Tanishq <[email protected]>
* Fix link check report inconsistency * Fix formatting issue --------- Co-authored-by: Tanishq <[email protected]>
* Restore trailing slash behaviour in serve command. * Restore guard in case where base_url is just a slash.
* Implemented bottom footnotes with backreferences Fixes #1285 * Added bottom_footnotes option to configuration.md * Renamed fix_github_style_footnotes() * Added tests for convert_footnotes_to_github_style() * Changed test to plain html instead of Vec<Event> * Added integration test for footnotes * Applied suggested changes
* Refine YAML date regex This commit does a few changes: - Introduce a new regex - it is a bit off-spec (it allows one-digit months and days in date-only mode) - uses named groups - avoids group duplication - parses offset once Fixes #2538 * Fix nanosecond parsing * Rename variables for brewity * Add tests
* Add feature to disable robots.txt and sitemap.xml from the config file. Addresses feature request #2248 * Add documentation for no_sitemap & no_robots * Rename no_robots and no_sitemap into generate_robots_txt and generate_sitemap (default to true) * fix rustfmt issues * Change documentation to show defaults * Update documentation for the fields generate_sitemaps (resp. robots_txt), now that the default is true and false is needed to disable
- Some error messages refer to `get_taxonomy_term_by_name` instead of `get_taxonomy_term` - If a term cannot be found in a taxonomy, the error message erroneously pretends that the taxonomy itself is unknown instead of the term.
Cleanup code by using `Option::is_some_and()` and `Option::as_deref()` instead of recoding them.
* update docs * add config option, logic, and tests * remove config option
…ion) (#2606) * Fix shortcode/continue-reading parsing with inline HTML (smaller version) * Remove inline <!-- more -->
Co-authored-by: GitHub Action <[email protected]>
Co-authored-by: GitHub Action <[email protected]>
The setup with Cloudflare Pages and the development environment with a Nix shell is documented. I believe this coudl be useful to others.
) This updates the Shortcodes documentation to specify that shortcode names must begin with a letter or an underscore. fixes #2654
Co-authored-by: GitHub Action <[email protected]>
Co-authored-by: GitHub Action <[email protected]>
The version in the snipped does not work. See issue: shalzz/zola-deploy-action#71
Co-authored-by: GitHub Action <[email protected]>
Co-authored-by: GitHub Action <[email protected]>
* Added tags support for themes * Docs: updated theme creation documentation, adding the tags optional variable * Changed taxonomy name to `theme-tags` * Revert "Changed taxonomy name to `theme-tags`" This reverts commit 2afd6db. * resolving * resolve * Search by tags not shown if no content with `theme-tags` taxonomy is provided
Co-authored-by: GitHub Action <[email protected]>
* Update Zola build deploy version to v0.19.2 * Fixed taxonomy now * Added more information for the themes
Co-authored-by: GitHub Action <[email protected]>
The package hasn't been updated since Zola 0.12
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.
See Commits and Changes for more details.
Created by pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )