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

familiarized myself with the repo #560

Merged
merged 6 commits into from
Jun 30, 2023
Merged

familiarized myself with the repo #560

merged 6 commits into from
Jun 30, 2023

Conversation

Brocktho
Copy link
Contributor

I have a formatter that made a lot of tweaks, All tests should run fine and behave. Main thing added was to dev.ts and server/dev.ts Just adding args. I also started looking at other parts of the repo, and added a markup.ts file into the react folder. I can remove it as it currently does nothing, but was planning to use it for a future commit.

Also used the data object export in the todos app example instead since it seems like more commonly users would want an async function that syntax supports async.

Let me know what changes if any are needed to add this in.

@deno-deploy deno-deploy bot had a problem deploying to Preview June 20, 2023 13:30 Failure
@deno-deploy deno-deploy bot had a problem deploying to Preview June 20, 2023 16:00 Failure
@ije
Copy link
Member

ije commented Jun 20, 2023

try upgrade https://esm.sh/v113/[email protected] to https://esm.sh/v126/[email protected]

@deno-deploy deno-deploy bot had a problem deploying to Preview June 20, 2023 16:20 Failure
@ije
Copy link
Member

ije commented Jun 20, 2023

oh, can you pls replace all esm.sh/v113 to esm.sh/v126?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what this file for? i did see you import it

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I started adding some stuff for a possible future feature, realized it might be too large to just add in and that's an artifact from that. I was going to use it to scrub markup data from loader data and that sort of thing. I can remove it for the time being, I should probably open an issue discussing changes I'd want to work on/implement for the project.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First big issue I have to report/figure out has to do with data coming from the data export on routes. I get very strange results. I'll write something up to display that issue and give possible solutions

Copy link
Member

@ije ije left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm! thank!!?(let's just ignore the lint error of deno.run in the pr)

@ije ije merged commit 901a9bb into alephjs:main Jun 30, 2023
3 of 4 checks passed
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