Scaffolding a type after a message throws an error

[fadeev]

Inside a brand new chain:

~/blog % starport s message create-post foo bar

modify proto/blog/tx.proto
create testutil/nullify/nullify.go
modify x/blog/client/cli/tx.go
create x/blog/client/cli/tx_create_post.go
modify x/blog/handler.go
create x/blog/keeper/msg_server_create_post.go
modify x/blog/types/codec.go
create x/blog/types/message_create_post.go
create x/blog/types/message_create_post_test.go

🎉 Created a message `create-post`.

~/blog % starport s type post foo bar          
component type with name post is already created (type MsgCreatePost exists)

Looks like we're checking for messages when scaffolding a type.

[lumtis]

I think type uses the same checking routines as other types before scaffolding and therefore --no-message must be used even though it doesn't have CRUD operations
We should change the checks for this type

[salmad3]

Will attempt to reproduce to see if still valid.

[julienrbrt]

This is still valid:

(main ✓) gm ignite s message create-post foo bar

modify proto/gm/gm/tx.proto
create x/gm/keeper/msg_server_create_post.go
modify x/gm/module/autocli.go
modify x/gm/module/simulation.go
create x/gm/simulation/create_post.go
modify x/gm/types/codec.go
create x/gm/types/message_create_post.go
create x/gm/types/message_create_post_test.go

🎉 Created a message `create-post`.

(main U:8 ?:4 ✗) gm ignite s type post foo bar     
Your saved project changes have not been committed.
To enable reverting to your current state, commit your saved changes.
Do you want to proceed without committing your saved changes: y
✘ Component type with name post is already created (type MsgCreatePost exists)