🐷 Please keep parameters compatible with future new models when upgrading

When going from 5 to 5.1, ā€œminimalā€ was changed to ā€œnoneā€. I assume keeping minimal as the passed argument would have given an error. I don’t know for a fact, because I painfully changed all of mine to match the new parameter. However, I don’t want to do this for every upgrade. The 5.1 should have accepted ā€œminimalā€ and behind the scenes re-route it to ā€œnoneā€ with a user info message notifying minimal is considered as none. This is very important for plug-n-play of new models, as I am sure you understand.

Please have a dedicated documentation team of interns; since software jobs are difficult to obtain, this would be a good start while still in school. The documentation has improved with updates but it is still severely lacking. Even Gpt 4o mini could improve it on first round.

1 Like