Improve humidity detection using 'in' operator

[lindnjoe]

• Changed condition from 'humidity !== null' to checking if 'humidity' key exists in object
• More reliable detection using 'in' operator instead of value check
• Will display humidity section even if value is temporarily null/undefined
• Prevents reactivity issues with undefined properties

Description

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings

[optional] Are there any post-deployment tasks we need to perform?

[chatgpt-codex-connector]

💡 Codex Review

mainsail/src/components/panels/Temperature/TemperaturePanelListItem.vue

Lines 234 to 237 in f55afc9

	get hasHumidity(): boolean {
	// Check if this sensor has a humidity property
	return 'humidity' in this.printerObject
	}

Ensure humidity visibility reacts when property is added

The new hasHumidity getter only evaluates 'humidity' in this.printerObject without touching this.printerObject.humidity. Because the Vuex mutation updates humidity via Vue.set(state[key], subkey, value), the sensor object reference stays the same and this computed value is never invalidated after the initial render. If the printer object is created without a humidity key and the key is added later (which is the normal lifecycle for these sensors), hasHumidity will remain false and the humidity row will never appear, despite data arriving. The previous v-if="humidity !== null" depended on the humidity computed getter and updated correctly. Consider basing hasHumidity on this.printerObject.humidity (or this.humidity !== undefined) so the dependency is reactive.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".