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

How to treat code generation? #14

Open
Klafyvel opened this issue Jan 28, 2023 · 0 comments
Open

How to treat code generation? #14

Klafyvel opened this issue Jan 28, 2023 · 0 comments
Labels
question Further information is requested

Comments

@Klafyvel
Copy link
Owner

Code generation is the most direct application of this package, hence it has been included almost since the beginning. However, if other code generation targets were to be added, we need to decide where to put them: here or in a separate repository.

The way I see things right now:

  • The main code generation utilities can stay within Norg.jl
  • Pandoc JSON could be in its own repository.
  • HTML generation is quite valuable when working in notebooks, but to reduce dependencies, we could use the new weak references to make it available only if Hyperscript.jl is available.
@Klafyvel Klafyvel added the question Further information is requested label Jan 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant