Check invalid elements in <Blocks> and <Input> strictly #64
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By adding input-compatible props to existed interactive components (#63), the possibility of wrong usage would increase. For example, using
label
prop at interactive components in<Blocks>
and<Actions>
would not be thrown error but outputs invalid JSON when sending to Slack.For helping user to notice mistake, we've refactored JSX parse logic and added after-parse validation to
<Blocks>
and<Input>
.Especially these were hard to check rendered elements if is used multi-level
<Fragment>
, so we changed internal JSX object to allow defining event function called at after parsed as internal props. Thereby we can validate to the final output of JSON.