Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Implement the remaining unimplemented server endpoints

Open
#439 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 4 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
api, backend

Research direction

Start by reading server/app/interfaces/repository.py, where the remaining unimplemented server endpoints are documented. Inventory the endpoints and determine their individual scope, usefulness, and implementation difficulty before selecting work. Done means the selected endpoints are implemented and their behavior is verified, though the issue does not name specific tests or verification steps.

Written by the indexing model from the issue text.

Description

feature server

There are still quite a few unimplemented server endpoints, they are currently documented in server/app/interfaces/repository.py.
I think it is worth taking another look at them and evaluating how difficult and useful it would be to implement them.

Sub-issues

Grouped by underlying mechanism rather than endpoint path (supersedes #528, #529, #530, #531):

  • #492 GET /description
  • #491 GET /serialization
  • #493 GET/PUT/DELETE /shells/{aasIdentifier}/asset-information/thumbnail
  • #644 $value serialization modifier for GET requests
  • #645 $value serialization modifier for PATCH requests
  • #643 $path serialization modifier
  • #646 PATCH endpoints for Submodels and SubmodelElements

Not planned: the Operation routes (invoke, invoke-async, operation-status, operation-results),
see #532.

Dominant language
Python
Stars
104
Forks
56
Avg merge
12d 13h
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-basyx/basyx-python-sdk

All issues in eclipse-basyx/basyx-python-sdk

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.