What's is more appropriate name for a method?

IsUserExists
DoesUserExist

Does makes more sense imo

Would probably have skipped both and just used UserExists.

If(UserExists)

Reads better tbh. Otherwise does.

I personally follow those rules:
consistency > case > grammar

So DoesUserExist, only and only if the rest of your code follows the same pattern.

I'm with @biglars: UserExists

IsUseistDoes, waste more time.

I like forming method names as direct questions, so I'd use UserExists.

UHazUser

@biglars it won't be much readable if I just return and don't use it in IF condition.

@xsid return object.UserExists

I think it's readable especially if it's a boolean.

IsUserCreated; //if it is about creation a user
IsUserAvailable; //If about doing stuff when the use is there

IsUserRecordFound // If it is about databases

I just create a exist() method in user object 🤔
If(User.exist())

It's based on consistency and constructs of the team. We have a lot of times where we use IsActive, IsAdmin, etc. If we were to introduce a new Boolean to check if a user exists, we would prefer to use IsUserExist to keep the naming consistent.

@irby Adding 'is' to a getter for a boolean is redundant, just drop it. Here it is also confusing as it contradicts the natural language.

If you wanna be sure that it's a boolean, your IDE will show you.

This is a good example of why it is bullshit to have "is" in the beginning of a bool variable or method or whatever.

I hate this convention/rule/requirement.

What about isExistingUser?

IsUserCreated
IsUserInitialized
IsUserExistent

@Commodore <—— what this guy said

The first one sounds like OG meme talk like "can i haz cheeseburger"

`thing.userExists(user)`

Or

`user.exists()`

@ojrask if it's something linked I'd prefer hasUser() or has(userObject)

@Lyniven true, makes more sense.

@Lyniven

I'd have had assumed this would be in a service or something. Why would you have a User object if you don't know if the user exists?

Fuck a function and method tbh.

@Superviral Care to expand?

UserIsAHumanBeingWhoAppearsInRealWorld

Found this discussion - https://softwareengineering.stackexchange.com/...

I would do something like userExists

isExistingUser

@bkwilliams CanHasUser

@delegate212 The user class not the object here sorry.
With model relation, if you have a comment with an user_id, the Comment.user() method will receive the user_id and do the query, it'll then check if the returned stuff is an *instance of* the given user class.
Dunno if I'm clear x) that's my way of doing stuff

TheCreatureWhoTakesAdvantageOfThisProductIsAHumanBeingWhoSeemsToBeVisiblyPresentAmongUsInThisPhysicalUniverseWeAllAreSimultaneouslyExperiencingAndParticipatingIn

UserCommitedExistance

How the fuck is this still going..