-
Notifications
You must be signed in to change notification settings - Fork 336
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
chore: remove google language manager #10639
base: master
Are you sure you want to change the base?
Conversation
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.
I just wanted to make sure you were not removing the GOOGLE_CLOUD variables, because they are also used for the GCP GCS file store. Good from my side.
Hey @mattkrick could you review this for @nickoferrall ? It's also useful for me, as it would remove one more thing from GCP 😸 I want to move the old PPMIs to their new GCP projects and I want to enable only useful APIs 😄 |
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.
I'm a bit concerned that the demo now operates VERY differently from what happens on the server, specifically that entities
won't exist on the server, but it still exists on the demo entities & there's server code that still shows a reference to it. That's gonna get really confusing for us as devs in 6 months from now when we forget what happened here.
My suggestion:
- get rid of all references to GoogleAnalyzedEntities (lemma, salience), including removing it from the GQL schema
- change the demo version of
updateReflectionContent
so the logic matches what the server version does. you can have it create a title with OpenAI or use a precanned version, but it shouldn't reference entities because those shouldn't exist anymore
.filter((word) => word.length > 3) // Skip small words | ||
.slice(0, 3) | ||
.join(' ') | ||
.toLowerCase() |
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.
+1 what about acronyms or proper nouns?
|
||
const getReflectionEntities = async (plaintextContent: string) => { | ||
const getBasicLemma = (word: string): string => { |
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.
-2 this is just too brittle. it'll only work on english, and even then words like "bread" and "Brent" are gonna get recognized as the same lemma. In cases like this, where there's a high likelihood of bad data, we're usually better of with just no data at all.
This PR removes the Google Language Manager now that we're using ChatGPT for reflection group titles (#10546).
The demo continues to use the entities logic.
This also removes the Sentiment Score logic. See Slack discussion here.
To test