Skip to content
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

Fixes issue #2 and uses pre-defined arguments instead of **kwargs #3

Conversation

h-janes
Copy link
Owner

@h-janes h-janes commented Nov 26, 2022

  • To fix predefining SERVER_NAME doesn't allow for flask serving multiple domains #2, URLs in the Sitemapper urls list are now stored as new URL objects rather than dicts, with methods that generate their URL loc and XML during sitemap generation. These changes are in sitemapper.py and templates.py

  • The Sitemapper methods include and add_endpoint previously accepted **kwargs but now only accept the pre-defined keyword arguments lastmod changefreqand priority

  • README.md has been improved and updated to reflect these changes.

  • A test has been added in test_server_name.py to ensure that the extension respects the SERVER_NAME if it is defined in the Flask configuration.

  • The version number has been incremented to 1.5.0 to reflect these changes and prepare for the next release.

@h-janes h-janes linked an issue Nov 26, 2022 that may be closed by this pull request
@h-janes h-janes merged commit c50ddcb into main Nov 26, 2022
@h-janes h-janes deleted the 2-predefining-server_name-doesnt-allow-for-flask-serving-multiple-domains branch November 26, 2022 22:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

predefining SERVER_NAME doesn't allow for flask serving multiple domains
1 participant