ip addr command setting incorrect subnet mask while assigning IP to an interface as compared to ifco

I am trying to set the IP address to an interface on my Ubuntu 18.04 machine using ip addr command however the ip addr command sets the subnet mask as 255.255.255.255 for a Class C IP address where as the ifconfig command sets the subnet mask as 255.255.255.0 for the same Class C IP address.

Sharing below the commands and their respective outputs.

ip addr command and its output.

nvidia@tegra-ubuntu:~$ sudo ip addr flush dev hv0                                                                                                                                                                               
nvidia@tegra-ubuntu:~$ sudo ip add 192.168.0.2 dev hv0
nvidia@tegra-ubuntu:~$ ifconfig
hv0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.2  netmask 255.255.255.255  broadcast 0.0.0.0
        ether 0a:86:4c:f8:4f:01  txqueuelen 1000  (Ethernet)
        RX packets 867  bytes 77026 (77.0 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 756  bytes 71072 (71.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 5  

ifconfig command and its output.

nvidia@tegra-ubuntu:~$ sudo ip addr flush dev hv0
nvidia@tegra-ubuntu:~$ sudo ifconfig hv0 192.168.0.2 up                                                                                                                                                                                       
nvidia@tegra-ubuntu:~$ ifconfig
hv0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.2  netmask 255.255.255.0  broadcast 192.168.0.255
        ether 0a:86:4c:f8:4f:01  txqueuelen 1000  (Ethernet)
        RX packets 867  bytes 77026 (77.0 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 756  bytes 71072 (71.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 5  

I would like to understand whether this is expected behavior or is this an issue with the ip addr command.

I also understand the mechanism to overcome this issue is to explicitly however I do not want to use them as if now and would like to understand the reason behind this change of behavior.