"odo nodejs create --port <>" creates component with invalid port

[prietyc123]

/kind bug

What versions of software are you using?

Operating System:
All supported

Output of odo version:
master

How did you run odo exactly?

$ git clone https://github.com/openshift/nodejs-ex frontend
Cloning into 'frontend'...
remote: Enumerating objects: 653, done.
remote: Total 653 (delta 0), reused 0 (delta 0), pack-reused 653
Receiving objects: 100% (653/653), 260.96 KiB | 292.00 KiB/s, done.
Resolving deltas: 100% (253/253), done.

$ cd frontend/

$ ls
README.md       openshift       server.js       views
helm            package.json    tests

$ odo create nodejs frontend --port hgsghsdewtgdshd
Validation
Warning: nodejs is not fully supported by odo, and it is not guaranteed to work
 ✓  Validating component [587ms]
Please use `odo push` command to create the component with source deployed

Actual behavior

It creates component for invalid port also.

Expected behavior

Suggestion : It would be great if we provide some hints like what could be possible port in the error message

Any logs, error output, etc?

Manually running the steps.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.