Issue when using `starport type [typeName]` with typeName is snake case

[duythien0912]

As a user when I create new type order_details command will throw error:

error while running command /tmp/nodetime: : exit status 1

vue/src/store/generated/duythien0912/minecat/duythien0912.minecat.minecat/module/index.ts(9,10): error TS2724: '"./types/minecat/tx"' has no exported member named 'MsgDeleteOrder_details'. Did you mean 'MsgDeleteOrderDetails'?
vue/src/store/generated/duythien0912/minecat/duythien0912.minecat.minecat/module/index.ts(11,10): error TS2724: '"./types/minecat/tx"' has no exported member named 'MsgCreateOrder_details'. Did you mean 'MsgCreateOrderDetails'?
vue/src/store/generated/duythien0912/minecat/duythien0912.minecat.minecat/module/index.ts(12,10): error TS2724: '"./types/minecat/tx"' has no exported member named 'MsgUpdateOrder_details'. Did you mean 'MsgUpdateOrderDetails'?
vue/src/store/generated/duythien0912/minecat/duythien0912.minecat.minecat/index.ts(6,10): error TS2724: '"./module/types/minecat/order_details"' has no exported member named 'Order_details'. Did you mean 'OrderDetails'?

We should convent [typeName] to camelCase when the user input snakeCase or a different case

Like:

order_details -> orderDetails

[fadeev]

Thanks, @duythien0912! Yes, I think we should do this 💯

[lumtis]

#977 is about generating a different case depending where the type name is used (kebab case for command name and camel case for variable name) so I think we may also implement in this task the idea of parsing and accepting any case in the command

[fadeev]

Fixed in #1236