update release notes for #8101

- As this is only a dev/testing dependency, and declaring the dependencies that you use directly is likely standard knowledge
- if anyone does overlook it, it'll presumably fail in an obvious and easily fixed way
- see 8ac683ef5c (r68486362)
pull/8113/head
LB Johnston 2022-03-15 08:10:16 +10:00
rodzic 8ac683ef5c
commit 7067c81604
1 zmienionych plików z 0 dodań i 5 usunięć

Wyświetl plik

@ -89,8 +89,3 @@ As of this release, the use of special-purpose field panel types such as `Stream
* If the panel provides a `get_comparison_class` method, your code should instead call `wagtail.admin.compare.register_comparison_class` to register the comparison class against the relevant model field type.
If you do continue to use a custom panel class, note that the template context for panels derived from `BaseChooserPanel` has changed - the context variable `is_chosen`, and the variable name given by the panel's `object_type_name` property, are no longer available on the template. The only available variables are now `field` and `show_add_comment_button`. If your template depends on these additional variables, you will need to pass them explicitly by overriding the `render_as_field` method.
### jinjalint replaced with curlylint
* Jinjalint is no longer actively maintained so the core Wagtail code has moved to a fork of this project [`curlylint`](https://github.com/thibaudcolas/curlylint).
* If your usage of Wagtail relies on the inclusion of [`jinjalint`](https://github.com/motet-a/jinjalint), you will now need to explicitly include this as a separate dependency.