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

Correctly parse executable #2

Merged
merged 1 commit into from
Dec 19, 2024
Merged

Correctly parse executable #2

merged 1 commit into from
Dec 19, 2024

Conversation

leo
Copy link
Member

@leo leo commented Dec 19, 2024

GitHub mistakenly displays the executable file that contains the Node.js shebang as JavaScript, even though the file has a .ts extension, indicating that it actually contains TypeScript.

My guess is that GitHub is doing this because Node.js, at the time of writing, does not natively support TypeScript, so we have to instruct GitHub to explicitly treat that file as TypeScript.

@leo leo added the enhancement New feature or request label Dec 19, 2024
@leo leo requested a review from colodenn December 19, 2024 12:20
Copy link

linear bot commented Dec 19, 2024

RON-1071 Ship "The Package", containing a portable version of RONIN

As the first major step towards making our entire product portable (meaning making it possible for people to actually "hold RONIN in their hands"), we would like to open-source a package named ronin, which effectively matches the programmatic signature of the current ronin package, except that the following must be ensured:

At the moment, RONIN only runs in the cloud, with the client being the main entry point into the cloud, since it serializes queries and sends them away, after which it receives a list of results to return from the client package.

Instead of requiring this interaction with the cloud, we would like to make it possible to run RONIN entirely standalone, such that anybody can run a RONIN database in the test suite of their application, in their migration script while testing changes, in a stateful application that would subscribe to the cloud version of RONIN, a local Electron app, or similar.

To accomplish this, we need to tackle all issues in Open-Source Data Layer, such that we can ultimately release a ronin package that imports the following logic pieces:

  • The logic for converting RONIN queries into SQL statements.
  • The logic for executing those SQL statements (the data layer).
  • The logic for converting the response of the data layer into usable records.

Furthermore, the package must expose programmatic functions for updating the schema definitions of a local database, such that all actions (regardless of whether a developer wants to query data or modify schemas) can be taken through the client package.

Copy link

Released an experimental package:

bun add @ronin/cli@leo-ron-1071-experimental-2

This package will be removed after the pull request has been merged.

@leo leo marked this pull request as ready for review December 19, 2024 12:21
@leo leo merged commit 8291341 into main Dec 19, 2024
3 checks passed
@leo leo deleted the leo/ron-1071 branch December 19, 2024 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants