@proxima-nexus/openapi 2.0.0 → 2.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +36 -0
- package/openapi.json +562 -68
- package/openapi.yaml +397 -57
- package/package.json +23 -23
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,42 @@ All notable changes to the Proxima Nexus OpenAPI specification are documented in
|
|
|
5
5
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
|
|
6
6
|
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
7
7
|
|
|
8
|
+
## [2.1.0] - 2026-03-02
|
|
9
|
+
|
|
10
|
+
### Added
|
|
11
|
+
|
|
12
|
+
- **Event series API**
|
|
13
|
+
- `POST /event-series`: create an event series from an RRULE and pre-generate all event instances. The creating user (or associated group) becomes the OWNER.
|
|
14
|
+
- `GET /event-series/{seriesId}`: fetch an event series definition.
|
|
15
|
+
- `PUT /event-series/{seriesId}`: update a series and propagate metadata changes to upcoming instances (per-instance overrides are preserved).
|
|
16
|
+
- `DELETE /event-series/{seriesId}`: delete a series and all upcoming event instances; past instances are preserved.
|
|
17
|
+
- `GET /event-series/{seriesId}/events`: list all event instances in a series, ordered by start time.
|
|
18
|
+
- **New schemas**: `CreateEventSeriesDto`, `EventSeriesDto`, and `UpdateEventSeriesDto` for creating, returning, and updating event series.
|
|
19
|
+
- **Event instances**: `EventDto` now includes an optional `seriesId` linking an instance back to its series.
|
|
20
|
+
|
|
21
|
+
### Changed
|
|
22
|
+
|
|
23
|
+
- **Event updates**: `PUT /event/{eventId}` summary clarifies how updates behave for instances in a series—fields supplied in the request body are treated as per-instance overrides and no longer follow series-level updates.
|
|
24
|
+
- **Validation**
|
|
25
|
+
- `UpdateUserDto`: `displayName` is no longer required; only `gender` and `birthDate` remain required.
|
|
26
|
+
- `CreateEventDto`: schema no longer requires `displayName`, `startTime`, `endTime`, or `type` (server-side validation may still enforce business rules).
|
|
27
|
+
- Group create/update DTOs that previously required `displayName` now only require `type`.
|
|
28
|
+
|
|
29
|
+
## [2.0.1] - 2026-02-04
|
|
30
|
+
|
|
31
|
+
### Changed
|
|
32
|
+
|
|
33
|
+
#### Connection state enums
|
|
34
|
+
|
|
35
|
+
- **User connections** (`GET /user/{userId}/connections` query filter and connection DTOs): state enum `requested` | `active` | `rejected` | `blocked` → `incoming_request` | `outgoing_request` | `active`.
|
|
36
|
+
- **Event connections** (`GET /event/{eventId}/connections` query filter and connection DTOs): state enum `requested` | `active` | `rejected` | `blocked` → `requested` | `active` | `invited`.
|
|
37
|
+
- **Group connections** (connection DTOs): state enum aligned with the same values as event connections: `incoming_request` | `outgoing_request` | `active` | `requested` | `invited`.
|
|
38
|
+
|
|
39
|
+
#### Connection DTOs (User, Event, Group)
|
|
40
|
+
|
|
41
|
+
- **EntityConnectionDto** and related connection response DTOs: `state` is no longer in `required`; only `type` is required.
|
|
42
|
+
- **type** enum: removed duplicate `admin` and `owner` values from connection type enums.
|
|
43
|
+
|
|
8
44
|
## [2.0.0] - 2025-01-29
|
|
9
45
|
|
|
10
46
|
### Breaking changes
|