Skip to content

Conversation

@Yang-33
Copy link
Contributor

@Yang-33 Yang-33 commented Apr 9, 2025

In the Messaging API webhook, we use discriminator to differentiate classes based on the value of type. During the development of bot SDK for Ruby v2, it seems that only Source does not have type marked as required. This is simply a mistake. The type should always be included to distinguish the kind of JSON, and there should not be any instances where it is absent.

@github-actions
Copy link

github-actions bot commented Apr 9, 2025

NODEJS

You can check generated code in nodejs

Check the diff here

@github-actions
Copy link

github-actions bot commented Apr 9, 2025

JAVA

You can check generated code in java

Check the diff here

@github-actions
Copy link

github-actions bot commented Apr 9, 2025

PYTHON

You can check generated code in python

Check the diff here

@github-actions
Copy link

github-actions bot commented Apr 9, 2025

GO

You can check generated code in go

Check the diff here

@github-actions
Copy link

github-actions bot commented Apr 9, 2025

PHP

You can check generated code in php

Check the diff here

@Yang-33 Yang-33 self-assigned this Apr 9, 2025
@Yang-33 Yang-33 requested a review from a team April 9, 2025 06:06
@Yang-33 Yang-33 enabled auto-merge April 9, 2025 06:08
Copy link
Contributor

@eucyt eucyt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@Yang-33 Yang-33 added this pull request to the merge queue Apr 9, 2025
Merged via the queue into main with commit 2f38058 Apr 9, 2025
20 checks passed
@Yang-33 Yang-33 deleted the add-type-as-required-propeorty-in-source-in-webhook branch April 9, 2025 06:22
Yang-33 pushed a commit to line/line-bot-sdk-php that referenced this pull request Apr 9, 2025
line/line-openapi#103

In the Messaging API webhook, we use `discriminator` to differentiate
classes based on the value of `type`. During the development of bot SDK
for Ruby v2, it seems that only `Source` does not have `type` marked as
required. This is simply a mistake. The type should always be included
to distinguish the kind of JSON, and there should not be any instances
where it is absent.

---------

Co-authored-by: github-actions <[email protected]>
Yang-33 pushed a commit to line/line-bot-sdk-python that referenced this pull request Apr 9, 2025
line/line-openapi#103

In the Messaging API webhook, we use `discriminator` to differentiate
classes based on the value of `type`. During the development of bot SDK
for Ruby v2, it seems that only `Source` does not have `type` marked as
required. This is simply a mistake. The type should always be included
to distinguish the kind of JSON, and there should not be any instances
where it is absent.

Co-authored-by: github-actions <[email protected]>
Yang-33 pushed a commit to line/line-bot-sdk-go that referenced this pull request Apr 9, 2025
line/line-openapi#103

In the Messaging API webhook, we use `discriminator` to differentiate
classes based on the value of `type`. During the development of bot SDK
for Ruby v2, it seems that only `Source` does not have `type` marked as
required. This is simply a mistake. The type should always be included
to distinguish the kind of JSON, and there should not be any instances
where it is absent.

Co-authored-by: github-actions <[email protected]>
Yang-33 pushed a commit to line/line-bot-sdk-nodejs that referenced this pull request Apr 9, 2025
line/line-openapi#103

In the Messaging API webhook, we use `discriminator` to differentiate
classes based on the value of `type`. During the development of bot SDK
for Ruby v2, it seems that only `Source` does not have `type` marked as
required. This is simply a mistake. The type should always be included
to distinguish the kind of JSON, and there should not be any instances
where it is absent.

Co-authored-by: github-actions <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants