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

`thing_state` is a property but isn't available in a client

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
fastapi, python
Domain
api, backend

Research direction

Start by reproducing the issue with an lt.TestClient for a Thing and accessing thing_state, as described in the report. Trace the client-facing handling of Thing properties and add or update a unit test; done means thing_state can be read without an attribute error.

Written by the indexing model from the issue text.

Description

Describe the bug
The thing_state proeprty isn't available to client code

To Reproduce
Create a lt.TestClient for a Thing in a unit test (not tested for other client types). Try to access thing_state. Get an error that it doesn't exist

Expected behaviour
I'd expect the thing_state to be available to read as it is a property.

System:

  • OS: Ubuntu 24.04
  • Python version: 3.11
  • Version: 0.0.11

Additional context
Add any other context about the problem here.

Dominant language
Python
Stars
9
Forks
4
PR merge metrics
No merged PRs in 30d

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 labthings/labthings-fastapi

All issues in labthings/labthings-fastapi

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.