-
Notifications
You must be signed in to change notification settings - Fork 50
fix: Porting Ratel to Vite. #382
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
Open
MichelDiz
wants to merge
31
commits into
hypermodeinc:main
Choose a base branch
from
OpenDgraph:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…uration - Cleaned up HTML structure in loader.html for better readability by removing unnecessary line breaks and spaces. - Simplified JavaScript in loader.js by removing trailing commas and unnecessary line breaks. - Introduced a new Vite configuration file (vite.config.js) to set up the project with React and path aliases for easier imports.
…s, migration, query, UI, and index
- Deleted `graph.js`, `graph.test.js`, `helpers.js`, `queryVars.js`, and `utils.js` as they are no longer needed. - Removed `backup.js`, `cluster.js`, `connection.js`, `frames.js`, `index.js`, `query.js`, and `ui.js` reducers to streamline the codebase. - Cleaned up associated imports and references throughout the project.
- Added GraphParser class to handle graph data processing and node management. - Introduced helper functions for cookie management, server latency calculation, and URL sanitization. - Created reducers for backup, cluster, connection, frames, query, and UI state management. - Added tests for graph processing functionality (currently commented out). - Implemented query variable extraction utility. - Established main entry point for the application with React rendering.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@MichelDiz is attempting to deploy a commit to the Hypermode Team on Vercel. A member of the Team first needs to authorize it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
TL;DR: Modernizing Ratel — now running on Vite with updated tooling and recent NPM support. No more being stuck in the past.
PS. I need help with this vercel stuff. No idea what it expects from me.
Man, this took a lot of work.
I finally mustered the courage and (partially) finished porting Ratel to Vite. There's still a lot to do, but it's a start.
My goal here is to bring Ratel back to life. I've been trying to do that for years, but it was just too complex. so much legacy config, so much going on. I gave up at least eight times. But I finally got it working with ViteJS.
I considered other tools and even using TypeScript, but that path was getting messy again. That said, I think we’ve landed on a solid solution here.
I'm asking you all to take a look and help me smooth out the rough edges. There are still a bunch of minor UI bugs to address, but overall, it's functional.
A few things to keep in mind:
I removed a lot of stuff that I didn’t fully understand or seemed unnecessarily complex. Just to simplify things. My thinking is: if it’s really essential, someone will either add it back in or come up with something better than a five-year-old, unmaintained piece of code, right?
One last note: the library that connects to Dgraph via HTTP isn’t compatible with Vite. That’s something that needs to be addressed in their repo if folks still want to use it. I just switched over to good old fetch.
Checklist
CHANGELOG.md
file describing and linking tothis PR
docs repo staged and linked here