wilkerlucio/spec-coerce

Issues

• Regex cat spec doesn't seem to be coerced at all

  #40 opened 2 years ago by TuggyNE
  3

• 1.0.0-alpha15 doesn't compile in CLJS

  #38 opened 4 years ago by thenonameguy
  1

• coerce-structure overrides nested unqualified keys support

  #37 opened 4 years ago by mpenet
  0

• First class coercion contexts

  #30 opened 4 years ago by mpenet
  2

• Support for multi-specs?

  #27 opened 4 years ago by Astronought
  1

• add support for s/merge

  #32 opened 4 years ago by mpenet
  2

• `spec/and` precludes coercion

  #29 opened 5 years ago by vemv
  3

• parse-long and parse-double should cast numeric types

  #25 opened 5 years ago by WhittlesJr
  0

• Nilables don't work when specs are used

  #23 opened 5 years ago by LukasRychtecky
  0

• Coercing a sequence changes its order

  #22 opened 5 years ago by LukasRychtecky
  2

• Bad coercions for pos/neg/nat specs

  #21 opened 5 years ago by vemv
  4

• Throws error for a spec with an `or` form in the `:req-un` set of a `keys` form.

  #18 opened 5 years ago by nogden
  2

• Coercion to string has no effect

  #17 opened 6 years ago by nogden
  3

• Coerce doesn't work in cljs

  #8 opened 6 years ago by khmelevskii
  6

• Coercion for Decimal doesn't work as expected

  #15 opened 6 years ago by LukasRychtecky
  2

• coerce! attempts to call s/valid? on unqualified keywords

  #14 opened 6 years ago by stathissideris
  4

• is there a function that raise an exception when coerce fail?

  #6 opened 6 years ago by DogLooksGood
  9

• Is support for s/nilable on the roadmap?

  #9 opened 6 years ago by seancorfield
  3

• inst? coerce seems very strict

  #10 opened 6 years ago by seancorfield
  13

• Setup CLJS test with shadow + karma

  #13 opened 6 years ago by wilkerlucio
  0

• Behavior for specs defined as set literals

  #7 opened 6 years ago by vemv
  3

• 'coerce-structure' should accept a spec as an argument, like 'coerce'

  #3 opened 7 years ago by Frozenlock
  3