Skip to content

Conversation

ford-jones
Copy link
Contributor

@ford-jones ford-jones commented Aug 20, 2025

Includes a configuration option which allow's the toggling of cleanup capabilities for RangeTest results.

See: meshtastic/firmware#7703

Checklist before merging

  • All top level messages commented
  • All enum members have unique descriptions

Copy link
Member

@fifieldt fifieldt left a comment

Choose a reason for hiding this comment

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

This makes sense to me

* Bool indicating that the node should cleanup / destroy it's RangeTest.csv file.
* ESP32 Only
*/
bool clear = 4;
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we call it clear_on_reboot? Based on your firmware PR I think that's the intended functionality, correct?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Certainly, I will change that now 👍

@thebentern thebentern merged commit 34f0c81 into meshtastic:master Sep 3, 2025
1 of 2 checks passed
@ford-jones
Copy link
Contributor Author

@thebentern I'm just updating the firmware PR to reflect the same naming. Ran into a merge conflict since having rebased to develop but should be resolved nicely.

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.

3 participants