This repository has been archived by the owner on Jul 2, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 96
om/om.next #228
Comments
What is the confusion and where are you seeing |
@featheredtoast hi! |
Om next uses different namespaces. @featheredtoast is right, we default to
classic om.
…On Dec 20, 2017 4:09 AM, "Dmitriy Non" ***@***.***> wrote:
@featheredtoast <https://github.com/featheredtoast> hi!
Isn't om.next just a om with version 1.0.0+ ?
If so that means that om.next gets used by default, not om
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#228 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAB91A7E1RjXhJ_fa9xxEkx959GBsAf1ks5tCHp8gaJpZM4REmY->
.
|
ok, nice. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello!
Correct me if I'm wrong but chestnut includes om.next by default.
So README is a bit confusing.
The text was updated successfully, but these errors were encountered: