it’s finally a useful tool!
in the terminal screenshot, here’s what happened:
i displayed the info of the server test, which is on port 8080 and has two endpoints (since one of them is ‘*’, any endpoint will trigger an action).
after that I set the action of the endpoint ‘*’ (which means all) to be print_payload.
then i started the server, which made it start listening to the listed endpoints on port 8080.
when a POST was sent to the port in the endpoint log, the action print_payload was triggered.
I will now use this to check the payloads from another app of mine, and it’ll allow me to build it ready to ship (instead of for example debug the values with prints or something)
little tweaks
solved a simple bug that was making a infinite loop (main instantiating a class, the class calling another class and the other class asking main for the instance)
Implemented reflection, simple cache system and ensure methods.
Alright I created 3 things here:
- A DReflection class, which will have functions related to reflection
- A DInsurance class, which will have functions for ensuring stuff (like ensure a variable is a certain type or just throw an exception)
- A cache system which saves stuff in RAM so you don’t have to keep repeating a specific search (like searching all classes in a specific package)
plus, I needed a simple error handler so the user could tell whatever he wanted to happen in ensure functions, instead of just hardcoding a throw new IllegalArgumentException().
setting up project, starting with a class for reflection stuff
just doing some research and testing with javalin
setting up things (my first rust project!)
a lot of structural changes
changed a lot of the structure
created the first endpoint
changed from LocalDate and LocalTime to Instant
created insertion method for database
removed some useless code and stuff that didn’t make sense to the project
implemented a simple system with annotations to give IDs to deadline actions, that way the action can be defined easily in the POST and the metadata can be parsed based on the chosen action
structuring server with the main thread
pretty much just added a check for when the user tries to create a new object when he already has created one.
also removed a few debug stuff and added some TODOs
Made some changes for the sake of good manners and implemented a way for the user to implement a update handler
the user can receive the list of changes in the configuration and handle it as soon as it arrives, without to make the software detect the change (with polling for example)
about the other changes, I was creating an instance of the configuration object every time the file was changed, which does not help performance at all. Now I just update the one we already have.
dynamic variables system poc
I faced a LOT of errors while coding that.
last devlog I had pretty much all the idea of how I wanted it to be but it wasn’t implemented at all, so I started changing whatever I needed in the code for it to work (such as creating parsing methods, ways to bump Java field’s values into the yml, etc).
now it pretty much works, but I haven’t tried creating dynamic variables of more complex types and I also don’t have a smart way to update THE FILE whenever the user updates the variable, instead of the way around which already works.
Loading more…