replace explicit gibberisch with a hopeful better explanation
Thomas Klausner
2 years ago
568 | 568 | |
569 | 569 | These three methods list parameters that B<must> be included in the |
570 | 570 | authorization url, the post to request tokens, and the post to refresh |
571 | tokens respectively. It used to be this space was occupied by a completely | |
572 | gibberish but mostly legit-looking sentence - now it is a legit one that is | |
573 | about as helpful as the original one was, without being completely gibberish. | |
571 | tokens respectively. If you explicitly provide these lists of required | |
572 | parameters, and a user fails to provide one (or more) of the | |
573 | parameters, the generated error message can tell the user which | |
574 | parameters are missing. | |
574 | 575 | |
575 | 576 | =item C<{authorization,request,refresh}_optional_params> |
576 | 577 |