ajones / datasnap-node

Nodejs wrapper of the Datasnap REST api

🧪 Welcome to the laboratory of Aaron Jones, the brilliant scientist who's synthesizing the future one line of code at a time!

🔍 In my quest for knowledge and self-improvement, I traverse the vast digital landscape, exploring new technologies to refine my skills and make the virtual world a better place.

🤝 Collaboration is the key to success in our interconnected world, so feel free to explore my repositories, contribute to my projects, or simply reach out to share a bug, an idea, or discuss the latest tech trends.

🌱 I firmly believe that growth and learning are never-ending journeys, and I'm always eager to take on new challenges and master new skills.

🎉 Let's band together and shape the future of technology with innovation, dedication, and a dash of fun! 💡👩‍💻🚀

datasnap-node's Issues

Future Dev of Datasnap nodesdk

Hi Aaron- here are my thoughts on the future dev of the nodesdk:
-- Some type of batching of event calls would be a good idea to deal with multiple events being sent concurrently- I think I will add this next and you can let me know your thoughts on it if you like
-- At this stage I think separate function calls for each event category is unnecessary for now. I think it might be a good idea to introduce validation on the data types in the json and when we do that it would then probably make sense to separate the validators for each event category.

Datasnap REST Endpoint not handling multiline JSON

Here is some information on the issue. Any way to reproduce in this driver so we can actively address on the REST API backend via error handling or handling of these multiline files properly if needed?

Our Curl example does use the following Multiline json:

https://gist.github.com/ryanmedlin/de374797dbb9c7a89e97

Example Curl Tests using our Test API keys:

https://gist.github.com/ryanmedlin/4fef493114cce8f55e5c

See Notes form Kate on the issue

BIG PROB: Sending JSON not in a single line and causes problems but don’t get an error if there is a new line – you just get partial JSON

• Getting a lot of errrors which is good For testing, Aaron was using a "prettified" version of json, over multiple lines so that the json string contains newlines and tab characters. json.stringify() was retaining the newline characters, and he thinks we were only looking at the first line. This was throwing weird errors at him that weren't overly obvious.