community: fix some features on Naver ChatModel & embedding model

[hyper-clova]

Description

• adding stopReason to response_metadata to call stream and astream
• excluding NCP_APIGW_API_KEY input required validation
• to remove warning Field "model_name" has conflict with protected namespace "model_".

cc. @vbarda

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
langchain	⬜️ Ignored (Inspect)	Visit Preview		Nov 20, 2024 8:14am

[efriis]

hey! any interest in deprecating this and moving to a self-managed partner package via this guide?

very similar to your original PR, just would be in a repo under your management instead of ours: https://python.langchain.com/docs/contributing/how_to/integrations/

[efriis]

(this is a new guide by the way - sorry it wasn't available during the initial integration - we're learning as a team!)

[hyper-clova]

@efriis , I waited for the updates because the docs were in draft version at the time you left the comments. Now I see the final version and will look into it.

For clarification, do you have plan for deprecating langchain-community then? (if yes, in what is the expected timeline?)

From our perspective, we just announced to our users about our integration availability this month, so we want to maintain in this way for a moment. (Also we have several upcoming minor fixes, wishing to be updated via community package like this issue.)

But as we are preparing a new API spec in next year (about 2Q), it might be ok then to migrating to a self-managed partner package as you mentioned. Would like to hear your thought on whether it is ok with this timeline.