- 
                Notifications
    
You must be signed in to change notification settings  - Fork 3
 
DX-1821: Deprecate Llms #40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
5fc5473    to
    493b571      
    Compare
  
    There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We also need to remove/deprecate api fields (like in dlq filter/event filter/messages/destinations/... etc).
| 
           I think there is a model-provider mismatch here, same for async test:  | 
    
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there is one more leftover api field that should be removed:
see message.py#298
        
          
                README.md
              
                Outdated
          
        
      | ```python | ||
| from qstash import QStash | ||
| from qstash.chat import upstash | ||
| from qstash.chat import openai | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
now, there is a duplicate example. see the line 103, Publish a JSON message to LLM Using Custom Providers
we should remove this or that
| 
           Apart from this PR, I think we have renamed events to logs in JS SDK, we can make the same here and remove the events api altogether since this is a major version bump  | 
    
No description provided.