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

move setRenderer for ssr to vdom.nim #207

Closed
wants to merge 2 commits into from
Closed

move setRenderer for ssr to vdom.nim #207

wants to merge 2 commits into from

Conversation

bung87
Copy link
Contributor

@bung87 bung87 commented Jun 4, 2021

No description provided.

@bung87
Copy link
Contributor Author

bung87 commented Jun 4, 2021

move to bigger patch #208

@bung87 bung87 closed this Jun 4, 2021
@bung87 bung87 reopened this Jun 20, 2021
@Araq
Copy link
Collaborator

Araq commented Jul 31, 2021

What is the goal of this PR? setRenderer does not belong to vdom.nim

@bung87
Copy link
Contributor Author

bung87 commented Jul 31, 2021

karax.nim import js target only module, that will cause compile time error, so I move to vdom.nim

@Araq
Copy link
Collaborator

Araq commented Jul 31, 2021

Can you move it into its own module instead?

@bung87
Copy link
Contributor Author

bung87 commented Jul 31, 2021

so user need import extro module, what's the module name ? I have no idea.

@Araq
Copy link
Collaborator

Araq commented Aug 11, 2021

I just realized that I don't understand the purpose of setRenderer so I cannot give you good advice to where it belongs.

@bung87
Copy link
Contributor Author

bung87 commented Aug 11, 2021

it renders to c backend and generate html to a relative path.

@Araq
Copy link
Collaborator

Araq commented Aug 11, 2021

Then it should be renamed to something else and vdom can contain it.

@bung87
Copy link
Contributor Author

bung87 commented Aug 12, 2021

so what it should be named ?

@Araq
Copy link
Collaborator

Araq commented Aug 12, 2021

proc renderToFile*(file: string; renderer: proc (): VNode)

No command line handling required.

@geotre
Copy link
Collaborator

geotre commented Mar 2, 2023

@bung87 do you want to implement the proposed name change (and deprecate the old one) or should we close this PR?

@geotre geotre mentioned this pull request Mar 2, 2023
@geotre
Copy link
Collaborator

geotre commented Mar 23, 2023

I'm going to close this for now, but please let me know if you want to reopen it @bung87

@geotre geotre closed this Mar 23, 2023
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