wbcore 2.2.3__py2.py3-none-any.whl → 2.2.5__py2.py3-none-any.whl

wbcore/contrib/agenda/release_notes/1_0_0.md

@@ -1,13 +0,0 @@
-Date: 2023-04-26
-Module: Agenda
-Summary: Initial Release Note
-Version: 1.0.0
-
-## New Features
-- Bootstrap module versioning
-
-## Enhancements
-./.
-
-## Bugfixes
-./.

wbcore/contrib/authentication/release_notes/1_0_0.md

@@ -1,13 +0,0 @@
-Date: 2023-04-26
-Module: Authentication
-Summary: Initial Release Note
-Version: 1.0.0
-
-## New Features
-- Bootstrap module versioning
-
-## Enhancements
-./.
-
-## Bugfixes
-./.

wbcore/contrib/currency/release_notes/1_0_0.md

@@ -1,13 +0,0 @@
-Date: 2023-04-26
-Module: Currency
-Summary: Initial Release Note
-Version: 1.0.0
-
-## New Features
-- Bootstrap module versioning
-
-## Enhancements
-./.
-
-## Bugfixes
-./.

wbcore/contrib/directory/release_notes/1_0_0.md

@@ -1,13 +0,0 @@
-Date: 2023-04-26
-Module: Directory
-Summary: Initial Release Note
-Version: 1.0.0
-
-## New Features
-- Bootstrap module versioning
-
-## Enhancements
-./.
-
-## Bugfixes
-./.

wbcore/contrib/directory/release_notes/1_0_1.md

@@ -1,13 +0,0 @@
-Date: 2023-05-10
-Module: Directory
-Summary: Employee Employer Table improvements
-Version: 1.0.1
-
-## New Features
-./.
-
-## Enhancements
-- Streamlined Employee-Employer sub tables
-
-## Bugfixes
-- Don't delete the underlying employer/employer when deleting a employee employer relationship

wbcore/contrib/documents/release_notes/1_0_0.md

@@ -1,13 +0,0 @@
-Date: 2023-04-26
-Module: Document
-Summary: Initial Release Note
-Version: 1.0.0
-
-## New Features
-- Bootstrap module versioning
-
-## Enhancements
-./.
-
-## Bugfixes
-./.

wbcore/contrib/geography/release_notes/1_0_0.md

@@ -1,13 +0,0 @@
-Date: 2023-04-26
-Module: Geography
-Summary: Initial Release Note
-Version: 1.0.0
-
-## New Features
-- Bootstrap module versioning
-
-## Enhancements
-./.
-
-## Bugfixes
-./.

wbcore/contrib/io/release_notes/1_0_0.md

@@ -1,13 +0,0 @@
-Date: 2023-04-26
-Module: I/O
-Summary: Initial Release Note
-Version: 1.0.0
-
-## New Features
-- Bootstrap module versioning
-
-## Enhancements
-- Allow for an automatic view resource created from the view serializer for export
-
-## Bugfixes
-./.

wbcore/contrib/notifications/release_notes/1_0_0.md

@@ -1,13 +0,0 @@
-Date: 2023-04-26
-Module: Notification
-Summary: Initial Release Note
-Version: 1.0.0
-
-## New Features
-- Bootstrap module versioning
-
-## Enhancements
-./.
-
-## Bugfixes
-./.

wbcore/contrib/tags/release_notes/1_0_0.md

@@ -1,13 +0,0 @@
-Date: 2023-04-26
-Module: Tags
-Summary: Initial Release Note
-Version: 1.0.0
-
-## New Features
-- Bootstrap module versioning
-
-## Enhancements
-./.
-
-## Bugfixes
-./.

wbcore/docs/orderable.md

@@ -1,29 +0,0 @@
-# Orderable View
-
-An orderable view enables the user to freely reorder rows inside AG Grid by drag-and-drop.
-
-**NOTE**: As these changes are saved in a model field, this will change the order globally for each user! Reordering on a per-user basis requires a way more sophisticated approach that is currently out of scope. Please also keep in mind that this also means that different orders for different views of the same model are not possible.
-
-## Implementation Steps
-
-### Simple Reordering
-
-Reorder rows inside a basic list view. Also includes the first level of tree views (level 0).
-
-1. Add the `OrderableModel` from `wbcore.models.orderable` to your model and migrate. Set initial values for existing instances by either `Model.orderable_objects.reset_order()` or calling `save()` on every object.
-2. Add the `order` field to your serializer.
-3. Add the `OrderableMixin` from `wbcore.viewsets.mixins` to your viewset. If you have defined a viewset ordering, make sure to first order by `order`.
-4. Add both `reorderable_column="order"` and `reorderable_endpoint=reverse(f"{endpoint.basename}-reorder", args=["{{id}}"], request=self.request)` to your list display.
-
-### Tree Child Reordering
-
-We currently only support reordering the first child row (i.e. level 1).
-
-1. Add the `OrderableModel` from `wbcore.models.orderable` to your model and migrate. Also add the class variable `PARTITION_BY` to your class and set it to the name of the foreign key field to the child's parent to partition the order values based on the parent. In this case the order number is unique only for the parent and not over the entire model anymore. Set initial values for existing instances by either `Model.orderable_objects.reset_order()` or calling `save()` on every object.
-2. Add the `order` field to your serializer.
-3. Add the `OrderableMixin` from `wbcore.viewsets.mixins` to your viewset. If you have defined a viewset ordering, make sure to first order by `order`.
-4. Add both `tree_reorderable_column="order"` and `tree_reorderable_endpoint=reverse(f"{endpoint.basename}-reorder", args=["{{id}}"], request=self.request)` to **the parent's** list display.
-
-## Example
-
-For an example please take a look at _example_app/team_. In this case we wanted both level 0 (Team) and level 1 (Player) to be reorderable so this example incorporates both a simple reordering for the parent level and a tree child reordering for the child level.

wbcore/docs/reparent.md

@@ -1,13 +0,0 @@
-# Reparent View
-
-A reparent view enables the user to switch a child's parent object inside a tree view by drag-and-dropping the child inside the new parent. Please note that this is currently only supported with level 1 children inside the tree view.
-
-## Implementation Steps
-
-1. Add a `PARENT_FK` class variable to the child's model and set it to the field name of the foreign key to the parent.
-2. Add the `ReparentMixin` from `wbcore.viewsets.mixins` to your viewset.
-3. Add both `tree_reparent_pk_field=f"{pk_field_name}"` and `tree_reparent_endpoint=reverse(f"{endpoint.basename}-reparent", args=["{{id}}"], request=self.request)` to the parent's list display.
-
-## Example
-
-For an example please take a look at _example_app/team_. Drag-and-dropping a child (Player) inside a new parent (Team) will transfer this player to a new team.

wbcore/templates/reversion/compare_detail.html

@@ -1,19 +0,0 @@
-<style type="text/css">
-    /* minimal style for the diffs */
-    pre.highlight {
-        max-width: 900px;
-        white-space: pre-line;
-    }
-    del, ins {
-        color: #000;
-        text-decoration: none;
-    }
-    del { background-color: #ffe6e6; }
-    ins { background-color: #e6ffe6; }
-    sup.follow { color: #5555ff; }
-</style>
-
-
-{% include "reversion-compare/action_list_partial.html"  %}
-{% include "reversion-compare/compare_partial.html"  %}
-{% include "reversion-compare/compare_links_partial.html"  %}