On Mon, Jun 3, 2019 at 2:43 PM parth.mishra <[email protected]> wrote:
> Huh, that's strange that no documentation exists. Do people not design the > API spec and code stubs prior to development? I'm not familiar with Java > dev > processes so I don't know. > What would be even more strange is if this documentation _did_ exist at this point, since no one has done it ;-). It isn't that such documentation could not exist, it just isn't something we've created or generated to date. I've looked at a couple of the tools for doing it (like Swagger), and it seems like it is something that would be reasonably straight-forward to integrate into the project, it just needs to be discussed and done. I'd suggest two things: - Create an issue for it in the project JIRA tracker: https://issues.apache.org/jira/browse/GUACAMOLE - Contribute some documentation or code to the effort :-D > > I think in my case, I figure it'd just be easier to use ODBC and handle > things manually. Not preferable, but I simply don't have the time to parse > out and document the API behavior. > > Modifying the database directly should be fine, too - many people have scripted things like syncing LDAP users to the database, so, depending on what you're trying to do, there shouldn't be any issue with that. Please keep in mind, as has been mentioned recently on other threads, that the folks who contribute to this project do so on a volunteer basis. In the same way that you may not have the time to parse out and document the API behavior, we may not have the time to implement certain features or document things to the level of detail that everyone expects. In an open source project the best way to affect change in a direction that is important to you is to contribute to the project. -Nick
