[go: nahoru, domu]

Skip to content
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

💽 refactor(client): Optimize ModelsConfig Query Cache #2330

Merged
merged 2 commits into from
Apr 5, 2024

Conversation

danny-avila
Copy link
Owner
@danny-avila danny-avila commented Apr 5, 2024

Summary

The cache/state of modelsConfig was a bit complex/convoluted, also causing a weird bug when the app is loaded for the first time, causing all custom endpoints to auto-select the first model from the initial static data for openAI.

This fixes the highlighted issue but improves DX surrounding the models query data, removing more code than adding.

No observable changes should be created aside from the above fix.

Other changes

Attempted to remove eslint bypasses for exhaustive dependencies for useEffect. One such case creates infinite render, another doesn't. removed where it doesn't. made note where it does for other devs.

Change Type

  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • My code adheres to this project's style guidelines
  • I have performed a self-review of my own code
  • I have commented in any complex areas of my code
  • I have made pertinent documentation changes
  • My changes do not introduce new warnings
  • I have written tests demonstrating that my changes are effective or that my feature works
  • Local unit tests pass with my changes
  • Any changes dependent on mine have been merged and published in downstream modules.
  • New documents have been locally validated with mkdocs

@danny-avila danny-avila merged commit f6a8488 into main Apr 5, 2024
1 check passed
@danny-avila danny-avila deleted the modelQuery-refactor branch April 5, 2024 21:08
@mrtngrsbch
Copy link

Will this change result in a new release soon?

@danny-avila
Copy link
Owner Author

Will this change result in a new release soon?

Not necessarily but I am going to cut releases more often. Ideally weekly so updates are made more frequently.

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.

None yet

2 participants