You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users can mix and match frequency plans from different bands.
Why do we need this? Who uses it, and when?
When users set multiple FPs from different bands, the backend will return an error.
Since the console already fetches the Band ID, it would be easier to validate this client side.
Proposed Implementation
Check that every new plan added after the first one has the same band ID as the first one.
Bonus points if the dropdown is only populated with frequency plans in the same band as the first one.
Contributing
I can help by doing more research.
I can help by implementing the feature after the proposal above is approved.
I can help by testing the feature before it's released.
Summary
This is an extension of #6615
Current Situation
Users can mix and match frequency plans from different bands.
Why do we need this? Who uses it, and when?
When users set multiple FPs from different bands, the backend will return an error.
Since the console already fetches the Band ID, it would be easier to validate this client side.
Proposed Implementation
Contributing
Code of Conduct
The text was updated successfully, but these errors were encountered: