Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / julienrf/play-json-derived-codecs issues and pull requests
#24 - Support polymorphic types
Issue -
State: closed - Opened by julienrf over 8 years ago
#24 - Support polymorphic types
Issue -
State: closed - Opened by julienrf over 8 years ago
#24 - Support polymorphic types
Issue -
State: closed - Opened by julienrf over 8 years ago
#24 - Support polymorphic types
Issue -
State: closed - Opened by julienrf over 8 years ago
#23 - Documentation fixes
Pull Request -
State: closed - Opened by lkt over 8 years ago
- 4 comments
#22 - Improve support of edge cases
Issue -
State: closed - Opened by julienrf almost 9 years ago
#21 - class XXXXX is not a case class nor a case object
Issue -
State: closed - Opened by siderakis almost 9 years ago
- 6 comments
#21 - class XXXXX is not a case class nor a case object
Issue -
State: closed - Opened by siderakis almost 9 years ago
- 6 comments
#20 - Make it possible to use it with custom variant formats (rather than generated by Play macros)
Issue -
State: closed - Opened by julienrf almost 9 years ago
#20 - Make it possible to use it with custom variant formats (rather than generated by Play macros)
Issue -
State: closed - Opened by julienrf almost 9 years ago
#20 - Make it possible to use it with custom variant formats (rather than generated by Play macros)
Issue -
State: closed - Opened by julienrf almost 9 years ago
#20 - Make it possible to use it with custom variant formats (rather than generated by Play macros)
Issue -
State: closed - Opened by julienrf almost 9 years ago
#20 - Make it possible to use it with custom variant formats (rather than generated by Play macros)
Issue -
State: closed - Opened by julienrf almost 9 years ago
#20 - Make it possible to use it with custom variant formats (rather than generated by Play macros)
Issue -
State: closed - Opened by julienrf almost 9 years ago
#20 - Make it possible to use it with custom variant formats (rather than generated by Play macros)
Issue -
State: closed - Opened by julienrf almost 9 years ago
#20 - Make it possible to use it with custom variant formats (rather than generated by Play macros)
Issue -
State: closed - Opened by julienrf almost 9 years ago
#20 - Make it possible to use it with custom variant formats (rather than generated by Play macros)
Issue -
State: closed - Opened by julienrf almost 9 years ago
#19 - Play 2.4 support
Issue -
State: closed - Opened by julienrf almost 9 years ago
#19 - Play 2.4 support
Issue -
State: closed - Opened by julienrf almost 9 years ago
#19 - Play 2.4 support
Issue -
State: closed - Opened by julienrf almost 9 years ago
#19 - Play 2.4 support
Issue -
State: closed - Opened by julienrf almost 9 years ago
#19 - Play 2.4 support
Issue -
State: closed - Opened by julienrf almost 9 years ago
#19 - Play 2.4 support
Issue -
State: closed - Opened by julienrf almost 9 years ago
#19 - Play 2.4 support
Issue -
State: closed - Opened by julienrf almost 9 years ago
#19 - Play 2.4 support
Issue -
State: closed - Opened by julienrf almost 9 years ago
#19 - Play 2.4 support
Issue -
State: closed - Opened by julienrf almost 9 years ago
#18 - Handle custom discriminator and discriminator transform function using a `Reads[String]`
Issue -
State: closed - Opened by julienrf almost 9 years ago
- 1 comment
#18 - Handle custom discriminator and discriminator transform function using a `Reads[String]`
Issue -
State: closed - Opened by julienrf almost 9 years ago
- 1 comment
#18 - Handle custom discriminator and discriminator transform function using a `Reads[String]`
Issue -
State: closed - Opened by julienrf almost 9 years ago
- 1 comment
#17 - Rewrite the implementation based on shapeless or scala-assembly instead of macros
Issue -
State: closed - Opened by julienrf almost 9 years ago
- 1 comment
#17 - Rewrite the implementation based on shapeless or scala-assembly instead of macros
Issue -
State: closed - Opened by julienrf almost 9 years ago
- 1 comment
#17 - Rewrite the implementation based on shapeless or scala-assembly instead of macros
Issue -
State: closed - Opened by julienrf almost 9 years ago
- 1 comment
#17 - Rewrite the implementation based on shapeless or scala-assembly instead of macros
Issue -
State: closed - Opened by julienrf almost 9 years ago
- 1 comment
#17 - Rewrite the implementation based on shapeless or scala-assembly instead of macros
Issue -
State: closed - Opened by julienrf almost 9 years ago
- 1 comment
#17 - Rewrite the implementation based on shapeless or scala-assembly instead of macros
Issue -
State: closed - Opened by julienrf almost 9 years ago
- 1 comment
#17 - Rewrite the implementation based on shapeless or scala-assembly instead of macros
Issue -
State: closed - Opened by julienrf almost 9 years ago
- 1 comment
#16 - Execution exception MatchError
Issue -
State: closed - Opened by levinotik about 9 years ago
- 17 comments
#16 - Execution exception MatchError
Issue -
State: closed - Opened by levinotik about 9 years ago
- 17 comments
#16 - Execution exception MatchError
Issue -
State: closed - Opened by levinotik about 9 years ago
- 17 comments
#16 - Execution exception MatchError
Issue -
State: closed - Opened by levinotik about 9 years ago
- 17 comments
#16 - Execution exception MatchError
Issue -
State: closed - Opened by levinotik about 9 years ago
- 17 comments
#16 - Execution exception MatchError
Issue -
State: closed - Opened by levinotik about 9 years ago
- 17 comments
#16 - Execution exception MatchError
Issue -
State: closed - Opened by levinotik about 9 years ago
- 17 comments
#15 - custom validation error message
Issue -
State: closed - Opened by ubourdon over 9 years ago
- 2 comments
#15 - custom validation error message
Issue -
State: closed - Opened by ubourdon over 9 years ago
- 2 comments
#15 - custom validation error message
Issue -
State: closed - Opened by ubourdon over 9 years ago
- 2 comments
#14 - Feature that allows transforming a discriminator's value to a valid classname
Pull Request -
State: closed - Opened by meln1k over 9 years ago
- 1 comment
#14 - Feature that allows transforming a discriminator's value to a valid classname
Pull Request -
State: closed - Opened by meln1k over 9 years ago
- 1 comment
#14 - Feature that allows transforming a discriminator's value to a valid classname
Pull Request -
State: closed - Opened by meln1k over 9 years ago
- 1 comment
#14 - Feature that allows transforming a discriminator's value to a valid classname
Pull Request -
State: closed - Opened by meln1k over 9 years ago
- 1 comment
#14 - Feature that allows transforming a discriminator's value to a valid classname
Pull Request -
State: closed - Opened by meln1k over 9 years ago
- 1 comment
#14 - Feature that allows transforming a discriminator's value to a valid classname
Pull Request -
State: closed - Opened by meln1k over 9 years ago
- 1 comment
#14 - Feature that allows transforming a discriminator's value to a valid classname
Pull Request -
State: closed - Opened by meln1k over 9 years ago
- 1 comment
#14 - Feature that allows transforming a discriminator's value to a valid classname
Pull Request -
State: closed - Opened by meln1k over 9 years ago
- 1 comment
#14 - Feature that allows transforming a discriminator's value to a valid classname
Pull Request -
State: closed - Opened by meln1k over 9 years ago
- 1 comment
#13 - remove unnecessary macro paradise dependency when scala 2.11
Pull Request -
State: closed - Opened by xuwei-k over 9 years ago
- 1 comment
#13 - remove unnecessary macro paradise dependency when scala 2.11
Pull Request -
State: closed - Opened by xuwei-k over 9 years ago
- 1 comment
#13 - remove unnecessary macro paradise dependency when scala 2.11
Pull Request -
State: closed - Opened by xuwei-k over 9 years ago
- 1 comment
#13 - remove unnecessary macro paradise dependency when scala 2.11
Pull Request -
State: closed - Opened by xuwei-k over 9 years ago
- 1 comment
#13 - remove unnecessary macro paradise dependency when scala 2.11
Pull Request -
State: closed - Opened by xuwei-k over 9 years ago
- 1 comment
#13 - remove unnecessary macro paradise dependency when scala 2.11
Pull Request -
State: closed - Opened by xuwei-k over 9 years ago
- 1 comment
#13 - remove unnecessary macro paradise dependency when scala 2.11
Pull Request -
State: closed - Opened by xuwei-k over 9 years ago
- 1 comment
#13 - remove unnecessary macro paradise dependency when scala 2.11
Pull Request -
State: closed - Opened by xuwei-k over 9 years ago
- 1 comment
#12 - Compiler failure when subclasses are not imported in the scope
Issue -
State: closed - Opened by arturaz over 9 years ago
#12 - Compiler failure when subclasses are not imported in the scope
Issue -
State: closed - Opened by arturaz over 9 years ago
#12 - Compiler failure when subclasses are not imported in the scope
Issue -
State: closed - Opened by arturaz over 9 years ago
#12 - Compiler failure when subclasses are not imported in the scope
Issue -
State: closed - Opened by arturaz over 9 years ago
#12 - Compiler failure when subclasses are not imported in the scope
Issue -
State: closed - Opened by arturaz over 9 years ago
#12 - Compiler failure when subclasses are not imported in the scope
Issue -
State: closed - Opened by arturaz over 9 years ago
#12 - Compiler failure when subclasses are not imported in the scope
Issue -
State: closed - Opened by arturaz over 9 years ago
#11 - Getting a Variant.formatter for classes that contain an object that already has a Variant.formatter
Issue -
State: closed - Opened by makoConstruct over 9 years ago
- 12 comments
#11 - Getting a Variant.formatter for classes that contain an object that already has a Variant.formatter
Issue -
State: closed - Opened by makoConstruct over 9 years ago
- 12 comments
#11 - Getting a Variant.formatter for classes that contain an object that already has a Variant.formatter
Issue -
State: closed - Opened by makoConstruct over 9 years ago
- 12 comments
#11 - Getting a Variant.formatter for classes that contain an object that already has a Variant.formatter
Issue -
State: closed - Opened by makoConstruct over 9 years ago
- 12 comments
#11 - Getting a Variant.formatter for classes that contain an object that already has a Variant.formatter
Issue -
State: closed - Opened by makoConstruct over 9 years ago
- 12 comments
#11 - Getting a Variant.formatter for classes that contain an object that already has a Variant.formatter
Issue -
State: closed - Opened by makoConstruct over 9 years ago
- 12 comments
#11 - Getting a Variant.formatter for classes that contain an object that already has a Variant.formatter
Issue -
State: closed - Opened by makoConstruct over 9 years ago
- 12 comments
#11 - Getting a Variant.formatter for classes that contain an object that already has a Variant.formatter
Issue -
State: closed - Opened by makoConstruct over 9 years ago
- 12 comments
#10 - Allow to generate Reads and Writes separately
Issue -
State: closed - Opened by ploddi almost 10 years ago
- 1 comment
#10 - Allow to generate Reads and Writes separately
Issue -
State: closed - Opened by ploddi almost 10 years ago
- 1 comment
#10 - Allow to generate Reads and Writes separately
Issue -
State: closed - Opened by ploddi almost 10 years ago
- 1 comment
#10 - Allow to generate Reads and Writes separately
Issue -
State: closed - Opened by ploddi almost 10 years ago
- 1 comment
#10 - Allow to generate Reads and Writes separately
Issue -
State: closed - Opened by ploddi almost 10 years ago
- 1 comment
#10 - Allow to generate Reads and Writes separately
Issue -
State: closed - Opened by ploddi almost 10 years ago
- 1 comment
#10 - Allow to generate Reads and Writes separately
Issue -
State: closed - Opened by ploddi almost 10 years ago
- 1 comment
#10 - Allow to generate Reads and Writes separately
Issue -
State: closed - Opened by ploddi almost 10 years ago
- 1 comment
#10 - Allow to generate Reads and Writes separately
Issue -
State: closed - Opened by ploddi almost 10 years ago
- 1 comment
#9 - Package name not obvious
Issue -
State: closed - Opened by pathikrit almost 10 years ago
- 1 comment
#9 - Package name not obvious
Issue -
State: closed - Opened by pathikrit almost 10 years ago
- 1 comment
#9 - Package name not obvious
Issue -
State: closed - Opened by pathikrit almost 10 years ago
- 1 comment
#9 - Package name not obvious
Issue -
State: closed - Opened by pathikrit almost 10 years ago
- 1 comment
#9 - Package name not obvious
Issue -
State: closed - Opened by pathikrit almost 10 years ago
- 1 comment
#9 - Package name not obvious
Issue -
State: closed - Opened by pathikrit almost 10 years ago
- 1 comment
#8 - Where is this published?
Issue -
State: closed - Opened by pathikrit almost 10 years ago
- 2 comments
#8 - Where is this published?
Issue -
State: closed - Opened by pathikrit almost 10 years ago
- 2 comments
#8 - Where is this published?
Issue -
State: closed - Opened by pathikrit almost 10 years ago
- 2 comments
#8 - Where is this published?
Issue -
State: closed - Opened by pathikrit almost 10 years ago
- 2 comments
#8 - Where is this published?
Issue -
State: closed - Opened by pathikrit almost 10 years ago
- 2 comments
#7 - Full path for JsSuccess
Pull Request -
State: closed - Opened by dimitriho almost 10 years ago
- 1 comment
#7 - Full path for JsSuccess
Pull Request -
State: closed - Opened by dimitriho almost 10 years ago
- 1 comment