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.

Sign up for GitHub

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

Jump to bottom

naming convention #2

Open
ianhi opened this issue Jun 28, 2020 · 1 comment
Open

naming convention #2

ianhi opened this issue Jun 28, 2020 · 1 comment

Comments

@ianhi
Copy link
Owner

ianhi commented Jun 28, 2020

I think the naming convention is that the kernel side gets named to reflect the kernel - while the typescript side has a name prefixed with jupyter. I think this is bc the typescript side is kernel agnostic. SO for ipysegment it should really be

ipysegement (for python)
jupyter-segment (for typescript)

In theory if someone wanted to make a back end in a different kernel then they could just use the jupyter-segment typescript library and only write the kernel part in whatever language
@ianhi
Copy link
Owner Author

ianhi commented Jun 28, 2020

probs could just be a small standalone file explaining the above

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ianhi