Hi Rob, It's not replacing anything, userinfo is part of URI: https://en.wikipedia.org/wiki/Uniform_Resource_Identifier
It would be stranger to deal with user/pass imo since that'd be more of an abstraction. Den måndag 18 mars 2019 kl. 14:37:05 UTC+1 skrev Robert Crous: > > Hi all, > > I understand that `Uri(some_url)->userInfo` returns the result of > `parse_url(some_url)[user]` (and then optionally append ':' . [pass]). > > My question is: why are there no setters and getters available for `user` > and `pass`? > > I can't see any reason why having getters/setters available for user + > pass would disrupt anything and it seems fairly odd that the decision was > made to replace this with `getUserInfo` and `withUserInfo`. > > But is there a specific reason why this was done? > > And if not- is there any way this can be added to the spec for the URI > interface? > > Kind Regards, > > Rob > -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/2dcd9831-f382-4576-bf23-bcf3c03e402d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
