moonbitstack/moonctl/style

README
U
Bind
U
DataSource
U
DataSourceError
U
DdlColumn
U
DdlTable
U
DocVersion
U
Field
U
FuncFn
U
GenFile
U
Group
U
PgTarget
U
Plugin
U
Proto
U
ProtoEnum
U
ProtoEnumValue
U
ProtoField
U
ProtoMessage
U
ProtoOneof
U
ProtoService
U
Range
U
ReflectedColumn
U
Regen
U
Route
U
Rpc
U
Spec
U
SpecError
U
Style
U
StyleError
U
Template
U
TemplateError
U
TreeFile
U
TypeDef
U
Value
V
deps
V
gen_files_to_json
V
generate
V
generate_agent
V
generate_crud
V
generate_crud_from_ddl
V
generate_crud_from_reflection
V
generate_doc
V
generate_gql
V
generate_grpc
V
generate_model
V
generate_tree
V
generate_with
V
openapi_document
V
parse
V
parse_all
V
parse_ddl
V
parse_dsn
V
parse_gen_files
V
parse_lenient
V
parse_proto
V
pins
V
plugin_argv
V
plugin_from_json
V
plugin_request
V
port
V
proto_reserved_conflicts
V
render
V
resolve_import
V
scaffold_api
V
scaffold_docker
V
scaffold_kube
V
scaffold_model
V
scaffold_rpc
V
spec_from_json
V
spec_to_json
V
spec_to_value
V
swagger_ui_stub
V
tables_from_reflection
V
tree_plan

moonbitstack/moonctl/style does not have a README file

StyleError

pub suberror StyleError {
  BadStyle(String)
}

A --style template that is not <before>GO<through>ZERO<after>: either a marker is missing (go, zero), they are the wrong way round, or one is cased neither go/GO/Go nor zero/ZERO/Zero (gOZero, goZEro).

Case

source

type Case

The case a marker asks its words to be spelled in.

Style

source

pub struct Style {
  before : String
  through : String
  after : String
  head : Case
  tail : Case
}

A --style naming template (← goctl's --style), ready to spell names with. Build one with Style::parse, apply it with Style::format.

Style::format

source

fn Style::format(self : Style, name : String) -> String

Spell name in this style. name is split into words on _ and before each capital, the first word takes the GO marker's case and the rest take ZERO's, and they are joined with whatever stood between the markers.

Style::gozero

source

fn Style::gozero() -> Style

goctl's default style, gozero: every word lower-cased and run together.

Style::parse

source

fn Style::parse(s : String) -> Style raise StyleError

Read a --style template. It must contain GO and then ZERO — in any case, with anything before, between and after them:

Style::parse("gozero").format("welcome_to_go_zero")  // welcometogozero
Style::parse("goZero").format("welcome_to_go_zero")  // welcomeToGoZero
Style::parse("go_zero").format("welcome_to_go_zero") // welcome_to_go_zero
Style::parse("Go#zero").format("welcome_to_go_zero") // Welcome#to#go#zero

The GO marker's own casing (go, GO or Go) says how the first word is spelled, ZERO's says how every later word is, and what stands between the two markers is what stands between the words. A template missing a marker (go, zero), holding them in the wrong order, or casing one of them any other way (gOZero, goZEro) raises StyleError.

Source Files

style.mbt

Install

Download zip

moonctl (mctl) — a spec-driven code generator for MoonBit (← goctl): parse a .api service spec and emit compilable moonapi scaffolding (routes + handler stubs).

goctlcodegenscaffoldapimoonapimoonbitcli