We use Break Versioning. The version numbers follow a <major>.<minor>.<patch>
scheme with the following intent:
Bump | Intent |
---|---|
major | Major breaking changes -- check the changelog for details. |
minor | Minor breaking changes -- check the changelog for details. |
patch | No breaking changes, ever!! |
-SNAPSHOT
versions are preview versions for upcoming releases.
Oksa is currently experimental.
Supports top-level definitions and local overrides for transformers.
; clj -Sdeps '{:deps {fi.metosin/oksa {:mvn/version "1.0.0"} camel-snake-kebab/camel-snake-kebab {:mvn/version "0.4.3"}}}'
(require '[oksa.core :as o])
(require '[camel-snake-kebab.core :as csk])
(o/gql* {:oksa/name-fn csk/->camelCase
:oksa/directive-fn csk/->snake_case
:oksa/enum-fn csk/->SCREAMING_SNAKE_CASE
:oksa/field-fn csk/->Camel_Snake_Case
:oksa/type-fn csk/->PascalCase}
[[:foo-bar {:alias :bar-foo
:oksa/name-fn csk/->SCREAMING_SNAKE_CASE
:directives [:foo-bar]
:arguments {:foo-arg :bar-value}}
[:foo-bar]]
:naked-foo-bar
[:...
[:foo-bar]]
[:... {:on :foo-bar-fragment
:directives [:foo-bar]}
[:foo-bar]]])
; => "{BAR_FOO:Foo_Bar(FOO_ARG:BAR_VALUE)@foo_bar{Foo_Bar} Naked_Foo_Bar ...{Foo_Bar} ...on fooBarFragment@foo_bar{Foo_Bar}}"
oksa.core/explain
as a convenience function for malli.core/explain
oksa.alpha.api
for programmatic API access
#7
FragmentDefinition
and OperationDefinition
to have just
single SelectionSet as per specTypeName
to also support string-typed nameFirst release! 🎉
Can you improve this documentation? These fine people already did:
Ilmo Raunio & Raunio IlmoEdit on GitHub
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close