[SDESK-7441] Create basic async resource models and services for planning.events

[eos87]

Purpose

Implement the basic async resource and service for Planning Events app

What has changed

• Added resources models and services for Events, Planning, Assignments and Published
• Fixed pytests so they work with async
• Partially fixed behave tests (~82% of them now green)
• Updated GitHub actions to run with Python v3.10 and latest actions

Note

This PR depends on superdesk/superdesk-core#2758. Once that PR is merged, I will update the requirements here to point to superdesk-core async branch instead.

Thanks for checking!

[MarkLark86]

@eos87 I've had a quick look over it, looks fine so far. Will re-review once you've completed the schema changes etc

[eos87]

Hey @MarkLark86, I've made the changes and left a couple of comments in the "unresolved" conversations. I added this small helper method

superdesk-planning/server/planning/types/common.py

Lines 202 to 207 in b85a4e2

	@classmethod
	def to_elastic_properties(cls) -> dict[Literal["properties"], Any]:
	"""Generates the elastic mapping properties for the current dataclass"""
	json_schema = TypeAdapter(cls).json_schema()
	return json_schema_to_elastic_mapping(json_schema)

do you think this could be useful in other places? At the moment I'm using it like this

superdesk-planning/server/planning/types/planning.py

Lines 103 to 106 in b85a4e2

	"assigned_to": {
	"type": "object",
	"properties": CoverageAssignedTo.to_elastic_properties(),
	},

to avoid duplicating the same thing just in the form of a elastic mapping. I guess there would be other places where we would need something similar.

[MarkLark86]

Hey @MarkLark86, I've made the changes and left a couple of comments in the "unresolved" conversations. I added this small helper method

superdesk-planning/server/planning/types/common.py

Lines 202 to 207 in b85a4e2

	@classmethod
	def to_elastic_properties(cls) -> dict[Literal["properties"], Any]:
	"""Generates the elastic mapping properties for the current dataclass"""
	json_schema = TypeAdapter(cls).json_schema()
	return json_schema_to_elastic_mapping(json_schema)

do you think this could be useful in other places? At the moment I'm using it like this

superdesk-planning/server/planning/types/planning.py

Lines 103 to 106 in b85a4e2

	"assigned_to": {
	"type": "object",
	"properties": CoverageAssignedTo.to_elastic_properties(),
	},

to avoid duplicating the same thing just in the form of a elastic mapping. I guess there would be other places where we would need something similar.

Not sure there would be many other places where this would be used, as it's mostly covered by the new type system. This use case is an edge case, all others I can think of are for the storage and search of the data itself, so should be fine to leave where it is

[BrianMwangi21]

Hey @eos87 just a few more changes to some fields from mandatory to optional:

For EventResourceModel the following fields:

• name
• event_contact_info
• translations

For PlanningResourceModel the following fields:

• coverages.coverage_id
• coverages.assigned_to

[eos87]

@BrianMwangi21 fixed event_contact_info and translations providing default factory constructors for them. As for name I think it should be required. I suppose we should not create an event without a name at least.

Regarding PlanningResourceModel, coverage_id has been fixed. assigned_to had already a default factory constructor.

[BrianMwangi21]

Thanks. I'll see what to do about the names.