-
Try out the new Jake: AI Coding Assistant for LabVIEW!
Get answers to questions about LabVIEW and discuss your code.
Blue Formatter For LabVIEW by SAS Workshops - Toolkit for LabVIEW Download
Blue - Like Black, but for LabVIEW
Discussion
| Version | 4.0.0.975 |
| Released | Dec 30, 2025 |
| Publisher | SAS Workshops |
| License | MIT |
| LabVIEW Version | LabVIEW>=20.0 |
| Operating System | Windows, Mac, and Linux |
| Dependencies | felipefoz_lib_lv_rainbow_terminal sas_workshops_lib_filewatcher wiresmith_technology_lib_g_cli |
| Project links | Homepage Documentation Repository Discussion |
Description
An autoformatter for LabVIEW inspired by Python's Black, LabVIEW's own Nattify and Felipe Silva's experiments.
It can be run from the Tools Menu. This will open a GUI that allows you to run Blue on all files in your project. There is also an option to just run on files that have changed in Git as well from this GUI.
It can also be run as a G-CLI Tool. This can be really useful for Legacy Code.
In it's simplest form:
g-cli blue -- "Directory to Format"
It will find all VIs in the directory and run a set of autoformatting steps on them, similar to the Nattify Steps (in fact in the beginning exactly the Nattify, hopefully to be expanded in the future.)
For more info, see the readme here: https://gitlab.com/sas-blue/blue
Release Notes
- Enhanced support for Custom Step Classes.
- Added ability to add a ~/.blue/blue_steps.json to specify the steps to load. This allows for loading custom steps as well as reordering or completely skipping existing steps. See readme for details.
- Added new CLI option --create-template to create template for the step list file, in order to allow adding custom steps. Simply edit the template to add your custom step. Then remove the .template extension from the file and it should work. Blue will now include your custom step when running.
- Got rid of Steps Library. This avoids having to load all Steps if they aren't all used (ie. if a steps file is provided that doesn't include them)
- Updated API Utility methods to require class input. Needed to do this for ones that required the Path to the file that specifies steps to load. Default behavior should be ok in most cases. So it will require changes to calling code but in most cases create constant should suffice.
- Fixed bug/issue [#5] in gitlab. Shrinking named bundlers was shrinking IPES if one side is unwired. Changed to check both sides and only shrink when both sides are unwired.
- Updated name that shows up in the undo menu when running from quickdrop.
- Moved location inside vilib from SAS/Blue Auto Formatter to simply SAS/blue. It was too verbose and since it was a major rev anyway, I felt empowered. I don't think it should affect anyone. I mean there is a blue API, but I haven't advertised it and haven't talked to anyone who was using it. If you are using it LabVIEW should just find it at a slightly different path. You might get a warning but that should be it. If you are using the API and this change broke something, I apologize.
Post an Idea
Post a Resource