Skip to content

bluez.Device: Move fallbacks here from Base - #3242

Open
infirit wants to merge 1 commit into
blueman-project:mainfrom
infirit:propertyfallbacks
Open

bluez.Device: Move fallbacks here from Base#3242
infirit wants to merge 1 commit into
blueman-project:mainfrom
infirit:propertyfallbacks

Conversation

@infirit

@infirit infirit commented May 13, 2026

Copy link
Copy Markdown
Contributor

The fallbacks are for org.bluez.Device1 not everyting based on Base.

@infirit

infirit commented May 14, 2026

Copy link
Copy Markdown
Contributor Author

I disagree with sonarcloud here. This is an error and having the exception logged helps.

The fallbacks are for org.bluez.Device1 not everyting based on Base.
@infirit
infirit force-pushed the propertyfallbacks branch from cd1b6de to 5d59165 Compare May 31, 2026 14:36
@sonarqubecloud

Copy link
Copy Markdown

@infirit
infirit requested a review from cschramm May 31, 2026 14:37
@infirit

infirit commented May 31, 2026

Copy link
Copy Markdown
Contributor Author

Rebased and CI is clean.

@infirit
infirit enabled auto-merge (rebase) May 31, 2026 14:38
Comment thread blueman/bluez/Base.py
return property.unpack()
elif name in self.__fallback:
return self.__fallback[name]
elif self._fallbacks is not None and name in self._fallbacks:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is not None is redundant

Suggested change
elif self._fallbacks is not None and name in self._fallbacks:
elif name in self._fallbacks:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants