Hi Sebastiaan, Would this be sufficient for your use case: http://stackoverflow.com/questions/26500539/scala-getting-field-and-type-of-field-of-a-case-class
This can be put in a trait as a method and mix in to different case classes. If the name of the type signature is enough for your GUI that would be great. Regards, Donald On Tue, Oct 25, 2016 at 11:53 AM, Sebastiaan de Man <[email protected]> wrote: > Hi all, > > I'm building a GUI for PredictionIO that allows for easy sending of events > and querying the engine. It will have to be able to talk different Engines, > which all expect different event properties and have their own queries and > responses. > > What would be the best way to implement a mechanism that will provide a > json description, with expected types of the Query and PredictedResults? > I'm thinking it could either be done using scala.reflect, with maybe > annotations, however it should be easy to add it, maybe as a trait, to any > existing custom built engines. > > Any suggestions? Ideas? > > Many thanks! > > Sebastiaan de Man >
