fix: #363

[hazem3500]

closes #363

[shilman]

LGTM! Test would be nice 😉

[hazem3500]

I've tried writing a test but the test code was a bit difficult for me to "parse"(pun semi-intended 😅).
So it would be great if someone pointed me on how to write a test for this PR.
We would want to write a test for it should parse component without parameters in function statement or it shouldn't throw an error if the component doesn't have parameters in function statement, right?

[pvasek]

@hazem3500 I think the easiest way is to pick one of the existing test component from src/__tests__/data. The most simple one and closest to your case. If you find one, great, you can copy it name it as you want and you can also copy the original test and update it.

If there is no such component, don't worry, just create the most simple example you want to cover in src/__test__/data and create a test for it. The test can be harder to read because they use helpers for checking the expected results but once you try to put it together I am sure you will understand.

From what you suggest, the it should parse component without parameters in function statement seems better to me but that's just personal taste.

[hazem3500]

I've tried writing a test again, but I couldn't find a case where functionStatment.parameters is undefined

I thought maybe it's the typescript version, mine was 4.2.2 but after upgrading most of the test threw other errors 😅

[pvasek]

@hazem3500 ok, as the change is so small and obviously more robust. I am merging it without new tests.