-
Notifications
You must be signed in to change notification settings - Fork 1
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
Release 1.1.0 #253
Release 1.1.0 #253
Conversation
|
||
### Changed | ||
- Moved slug uniqueness validation to the model validation/clean | ||
- Empty slugs will auto-generate a unique slug, but if a duplicate slug is specified the user will get a validation error instead of their chosen slug getting overwritten with a unique one. | ||
- Slug uniqueness is per-locale | ||
- Test speedups. Tests now run in parallel by default, and there's a separate contentrepo/settings/test.py for test-specific settings. | ||
- Tests no longer run in parallel by default, because the output is a little less clear and the speedup is negligible on some systems. | ||
- WhatsApp example values no longer show on the default API view, and forms part of the fields returned when the parameter `whatsapp=true` is added to the api call | ||
- Improved testing of Importer |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe add the new importer to this? We mention removing the old one, but not adding the new one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the importer was added in the dev releases prior to this, but let me know if you strongly disagree?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, right. I missed the dev release sections.
It's fairly common for non-dev release changelogs to include all the relevant changes from the dev releases leading up to them, so people don't have to read a bunch of dev/beta/rc changelogs as well. I think not doing that here is fine, given that it would add a bunch of extra work and we're not really stable yet, but that's probably something for @rudigiesler to decide. 🤷
Create a stable release for 1.1.0