Plonemeeting.restapi

Latest version: v2.5

Safety actively analyzes 623144 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 6

2.6

----------------

- Nothing changed yet.

2.5

----------------

- When using `fullobjects`, only serialize `next/previous` when specifically
asked using `include_nextprev=true`.
[gbastien]

2.4

----------------

- Fixed `test_restapi_add_clean_meeting`, when generating new date use datetime
and timedelta to avoid generating an unexisting date,
here it was generating `2025/02/29` that does not exist.
[gbastien]
- When using `users?extra_include=categories`, categories are only returned if
enabled in `MeetingConfig`, same for `classifiers`, this avoid having
selectable categories for an user when categories are not used.
[gbastien]
- Added special behavior for `review_state` and `creators` when asked in
`metadata_fields`:

- `review_state` will return a token/title with review_state id
and translated title;
- `creators` will return a list of token/title with each creator id
and fullname.

[gbastien]

2.3

----------------

- Adapted code as `Products.PloneMeeting.utils.add_wf_history_action` was moved
to `imio.history.utils.add_event_to_wf_history` and
`ToolPloneMeeting.getAdvicePortalTypes` and
`ToolPloneMeeting.getAdvicePortalTypeIds` were moved to utils.
[gbastien]

2.2

----------------

- Always include `type` info in result even when `include_base_data=false` as
it is used with `UidSearchGet.required_meta_type_id`.
[gbastien]

2.1

----------------

- In `base.serialize_attendees`, do not use `UID` from serialized result as it
could not be there when using `include_base_data=false`.
[gbastien]

Page 1 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.