Add element create

[haneslinger]

No description provided.

[Copilot]

Pull request overview

Adds support for creating property “elements” via the SEED API client, alongside a couple of related client method enhancements.

Changes:

• Add a new properties_elements endpoint mapping and a create_element convenience method.
• Extend get_buildings to accept extra query filters.
• Extend meter creation payload to include connection_type.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.

File	Description
pyseed/seed_client_base.py	Adds the /api/v3/properties/PK/elements/ endpoint alias used by the client.
pyseed/seed_client.py	Adds create_element, extends get_buildings with filters, and adds connection_type to meter creation.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

get_buildings uses a mutable default argument (filters: dict = {}), which can leak state across calls if the dict is mutated. Use filters: Optional[dict] = None and set filters = filters or {} inside the method.

Suggested change

	def get_buildings(self, filters: dict = {}) -> list[dict]:
	def get_buildings(self, filters: Optional[dict] = None) -> list[dict]:
	filters = filters or {}

[Copilot]

Passing **filters alongside explicit keywords (per_page, page, cycle) will raise TypeError: got multiple values for keyword ... if filters includes any of those keys (e.g., callers may reasonably pass {"cycle": ...}). Build a params dict and update() with filters (or vice versa) to avoid duplicate-key errors and make precedence explicit.

[Copilot]

get_or_create_meter adds connection_type but it is missing a type annotation and is not documented in the docstring Args section. Please type it (e.g., str) and document what values are accepted/expected by the SEED API so callers know how to use it.

[Copilot]

total_qry is computed without cycle (and will also ignore any new filters), but the paged requests include cycle=self.cycle_id (and filters). This can inflate num_pages and cause unnecessary extra API calls; consider using the same query params for the initial pagination request as for the subsequent page fetches.