I think that calling it 'getUserNameRaw' is more appropriate since some people might get confused if we call it'getUserId()' whitch would give impression that this method returns primary key.
Regards Greg Bugaj --- On Mon, 8/25/08, Dave <[EMAIL PROTECTED]> wrote: From: Dave <[EMAIL PROTECTED]> Subject: Adding access to "real" username in UserWrapper To: [email protected] Date: Monday, August 25, 2008, 8:06 AM Roller allows you to have both a 'username' and a 'screenname'. Your username must be unique and can never change. Your sceenname doesn't have to be unique and can change. That's all good (perhaps I would have called the unique one 'userid' and the changing one 'username' if I had to do it all again, but no matter). In Roller page templates, when you access the $user.username property, you actually get the sceenname back, which is the right thing for most cases because that's what we want to display. That's all good too, but there are cases where you need access to the unique username identifier. Any objection to adding a way to access username in the UserWrapper object? And, what should the method be called? Should it be: UserWrapper.getUserId() Or: UserWrapper.getUserNameRaw() Or something else. I like the first option. - Dave
