fix(122): split switch state to separate file

[lsytj0413]

Signed-off-by: lsytj0413 511121939@qq.com

Many thanks for submitting your Pull Request ❤️!

What this PR does / why we need it:

Special notes for reviewers:

Additional information (if needed):

Fixed #122

[spolti]

can you please also add a test using yaml or json that have a invalid switch state (different than Data or Event based switch)? Just to make sure that the parser will complain if something unexpected is typed, e.g. a typo.

[lsytj0413]

can you please also add a test using yaml or json that have a invalid switch state (different than Data or Event based switch)? Just to make sure that the parser will complain if something unexpected is typed, e.g. a typo.

Can you explain more clearly (a example will be helpful). IMO, if the user set any field than specification, there will be no error reported (because we only unmarshal the known field).

[ricardozanini]

@spolti can you answer the comments? @lsytj0413 can you please rebase?
Sorry for the late reply, I was on PTO.

[spolti]

can you please also add a test using yaml or json that have a invalid switch state (different than Data or Event based switch)? Just to make sure that the parser will complain if something unexpected is typed, e.g. a typo.

Can you explain more clearly (a example will be helpful). IMO, if the user set any field than specification, there will be no error reported (because we only unmarshal the known field).

A good test could be marshall and unmarshall like we did here: https://github.com/serverlessworkflow/sdk-go/blob/main/parser/parser_test.go#L609

use a proposital type to define, let's say, "eventCondition", the result should be nil pointer or a error log telling the value is not valid,.

[lsytj0413]

A good test could be marshall and unmarshall like we did here: https://github.com/serverlessworkflow/sdk-go/blob/main/parser/parser_test.go#L609

use a proposital type to define, let's say, "eventCondition", the result should be nil pointer or a error log telling the value is not valid,.

done, PTAL

[lsytj0413]

@ricardozanini resolved conflict, PTAL

[spolti]

Many thanks. :)