Skip to content

feat: add cache for github api requests, update relative imports to alias, update spicetify types and more #926

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

Closed
wants to merge 3 commits into from

Conversation

sanoojes
Copy link
Contributor

Changes made

  • Changed all relative import paths to use the @/ alias for better maintainability.
  • Migrated the ESLint configuration using pnpm dlx @eslint/migrate-config .eslintrc.js to streamline linting setup.
  • Cache Github API Requests to indexedDb (cache for 7d)
  • Added Clear Cache Button in marketplace for Clearing Cache from indexedDb
  • Change deprecated husky install to husky in package.json
  • Update Packages
  • Fix Button Props

…config

- Changed all relative import paths to use the @/ alias for better maintainability.
- Migrated the ESLint configuration using `pnpm dlx @eslint/migrate-config .eslintrc.js` to streamline linting setup.
@sanoojes sanoojes requested a review from a team as a code owner March 24, 2025 09:26
@sanoojes sanoojes requested review from rxri and removed request for a team March 24, 2025 09:26
@sanoojes sanoojes changed the title feat: add cache for github api requests, update relative imports to alias, update spicetify types feat: add cache for github api requests, update relative imports to alias, update spicetify types and more Mar 24, 2025
@sanoojes sanoojes closed this by deleting the head repository Apr 9, 2025
@theRealPadster
Copy link
Member

Aww this looked good. I just didn't have a chance to actually test it or anything, so didn't want to just go ahead and merge it.

@rxri
Copy link
Member

rxri commented Apr 9, 2025

Aww this looked good. I just didn't have a chance to actually test it or anything, so didn't want to just go ahead and merge it.

I didn't allow it anyway due to caching process

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