Question
v1.0 wishlist for breaking features
Asked by: USER6226
35 Viewed
35 Answers
Answer (35)
Any backwards-incompatible changes we want to make to wifitui for cutting a v1.0 release?
- [ ] Change more of the
wifi.Backendinterface to take options structs rather than positional args (e.g. forJoinNetwork) - [ ] Do we want to consolidate
radiosubcommand intodevices? (Not sure about this one)
Answer:
To prepare for the v1.0 release of wifitui, here are some potential backwards-incompatible changes we can consider:
- Change more of the
wifi.Backendinterface to take options structs: Instead of using positional arguments, we can modify the interface to accept options structures for methods likeJoinNetwork. This would make the API more consistent and flexible. - Consolidate
radiosubcommand intodevices: This is an optional change. By merging theradiosubcommand into thedevicessubcommand, we can simplify the CLI and reduce redundancy. However, this change might cause conflicts with existing scripts that rely on the separateradiosubcommand.
**Important:** Making these changes will break compatibility with previous versions of wifitui. Users will need to update their code accordingly.