Could anyone explain why using layout like this?

[KeroZhai]

Like why pet, owner and visit are all in the package owner?

I'm having problem with layout in my own project, I'd appreciate it if someone could provide some suggestions, thanks in advance!

[Puravhirpara]

Like why pet, owner and visit are all in the package owner?

I'm having problem with layout in my own project, I'd appreciate it if someone could provide some suggestions, thanks in advance!

This is called feature-based packaging. Instead of splitting everything into separate folders by type (model, repo, controller), the code for a feature lives together in one package. It’s common in smaller projects and makes it easier to work on related code without jumping between packages

[gousik-Rao]

Like why pet, owner and visit are all in the package owner?
I'm having problem with layout in my own project, I'd appreciate it if someone could provide some suggestions, thanks in advance!

This is called feature-based packaging. Instead of splitting everything into separate folders by type (model, repo, controller), the code for a feature lives together in one package. It’s common in smaller projects and makes it easier to work on related code without jumping between packages

Thanks for your clear explanation!!

[KeroZhai]

Like why pet, owner and visit are all in the package owner?
I'm having problem with layout in my own project, I'd appreciate it if someone could provide some suggestions, thanks in advance!

This is called feature-based packaging. Instead of splitting everything into separate folders by type (model, repo, controller), the code for a feature lives together in one package. It’s common in smaller projects and makes it easier to work on related code without jumping between packages

Thanks for your reply, I know the feature-based packaging (and layer-based packaging). It's just naming this feature owner doesn't makes sense to me (maybe because I'm not a native :P). But after all, this project is only for demonstration, right? I shouldn't care about the name too much.

And I notice that you said:

It’s common in smaller projects and makes it easier to work on related code without jumping between packages

Does that mean the scale also matters and feature-besed packaging may not be suitable for large projects?

Still I found it's a little bit difficult to name the feature in my own project, and I'm not quite sure what stuff should go together. What is a feature exactly? How do we define it?