Now that Nexus framework is gone let's take back the name "Nexus".
Any objections @tgriesser?
Re-re-re name 馃槢 ? (gqliteral -> nexus -> @nexus/schema -> nexus)
But yeah, let's wait until 1.0 so there's less confusion, and since nexus got up to 0.30.1.
We can publish 1.0 to both, but deprecate @nexus/schema and un-deprecate nexus.
Yep was thinking the exact same thing, at 1.0
--edit
so maybe not next sprint, the one after
is the decision on framework really final? I would keep the current name IMO for future proofing...
If you want to split in multiple modules its also nicer because you have the @nexus namespace.
is the decision on framework really final?
Yep, if the framework comes back it will not be called Nexus
Make sense, I still think namespacing the modules is not a bad idea either since I see nexus as more of a plugin architecture than a monolith package.
It think having the package name match what people call it helps. And differentiating nexus from nexus schema, as if they mean something different, is confusing. YAGNI
closed by 80ad53135c98ab3cc816f7c6ddd652ce12a251ce
Most helpful comment
Re-re-re name 馃槢 ? (
gqliteral->nexus->@nexus/schema->nexus)But yeah, let's wait until 1.0 so there's less confusion, and since
nexusgot up to0.30.1.We can publish 1.0 to both, but deprecate
@nexus/schemaand un-deprecatenexus.