Currently our analysis capabilities are slightly limited in a few ways. For one, we only support return a float value for our analysis, a legacy idea that we will always return a score so to speak. This is likely the most common use case, but we have a generic data structure in the AresValue, so there's no reason not to use that instead. Adding on to this, we currently only support processing a single analysis at a time, another limiting factor that could be fixed with some structural updates to the messaging.
Given we have some real users at this point, it's probably worth a conversation on making this change without breaking people's old analyzers. Probably achievable by keeping the old properties and simply adding onto them moving forward.
Currently our analysis capabilities are slightly limited in a few ways. For one, we only support return a float value for our analysis, a legacy idea that we will always return a score so to speak. This is likely the most common use case, but we have a generic data structure in the AresValue, so there's no reason not to use that instead. Adding on to this, we currently only support processing a single analysis at a time, another limiting factor that could be fixed with some structural updates to the messaging.
Given we have some real users at this point, it's probably worth a conversation on making this change without breaking people's old analyzers. Probably achievable by keeping the old properties and simply adding onto them moving forward.