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.

Sign up for GitHub

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

Jump to bottom

Fix vite configuration #2777

Merged
merged 4 commits into from
Sep 20, 2024
Merged

Fix vite configuration #2777

merged 4 commits into from
Sep 20, 2024

Conversation

danigargar
Copy link
Contributor

Type Of Change

  • Small bug fix
  • New feature or enhancement
  • Breaking change

Checklist:

  • Commits are named and have tag following commit rules
  • Commits are split per component (schema, portal/platform, kamusers, agis, ..)
  • Changes have been tested locally
  • Fixes an existing issue (Fixes #XXXX)
  • Upport from existing Pull request #XXXX

Description

Additional information

@danigargar danigargar added +bug Bug portal/user User web interface portal/client Client portal portal/brand Brand portal portal/platform Platform portal *tempest* IvozProvider 4.x Tempest Release labels Sep 20, 2024
@danigargar danigargar added this to the 4.3.0 milestone Sep 20, 2024
@danigargar danigargar self-assigned this Sep 20, 2024
@danigargar danigargar changed the title Provider 2050 fix vite configuration Fix vite configuration Sep 20, 2024
@danigargar danigargar merged commit d616569 into bleeding Sep 20, 2024
10 checks passed
@danigargar danigargar deleted the PROVIDER-2050-fix-vite-configuration branch September 20, 2024 09:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@rbatistadev rbatistadev rbatistadev approved these changes

Assignees

@danigargar danigargar

Labels
+bug Bug portal/brand Brand portal portal/client Client portal portal/platform Platform portal portal/user User web interface *tempest* IvozProvider 4.x Tempest Release
Milestone
4.3.0
Development

Successfully merging this pull request may close these issues.
2 participants
@danigargar @rbatistadev