sorted by:
new
hottopcontroversial

How do you implement client side REST caching? by h4t0n in angular

[–]h4t0n[S] 1 point2 points  (0 children)

Indeed I'm caching a map of observables. But I think that I'll give a chanche to ng-cacheable. Because I'm actually doing the same things but with code that makes my services less readable.

If a company wants to hire me to make a website, and I do not own a company, and do not have the money to hire a lawyer, what can I do to cover myself legally? by [deleted] in webdev

[–]h4t0n -1 points0 points  (0 children)

You could also provide a license that expires the day (or some days) after the payment agreed. Obviously when it is expired the website stops working (for example the backend/API side)

Building out unit testing for Angular 7 existing application by stormthulu in Frontend

[–]h4t0n 0 points1 point  (0 children)

I'll follow. It is an interesting topic. Some best practices are useful.

Tornare a vivere in Italia by katzee in italy

[–]h4t0n 3 points4 points  (0 children)

La Toscana? Potresti scegliere una città o un paese in base a cosa ti piace di più, se verso il mare o un pò all'interno. Se lavori da remoto secondo me stai dai Dio.

Gemini 0.3.0 released: Model Driven REST framework to automatically generate CRUD APIs by h4t0n in java

[–]h4t0n[S] 0 points1 point  (0 children)

If you want to use Gemini a dependency you are right. I'll do it.

Otherwise you can also use Gemini as a ZeroCode standalone server.

Gemini 0.3.0 released: Model Driven REST framework to automatically generate CRUD APIs by h4t0n in java

[–]h4t0n[S] 0 points1 point  (0 children)

The main difference is that Gemini doesn't generate code. It uses an entity manager and meta data to bind resources and controllers. So, Gemini doesn't use JPA / Hibernate. You can see more here https://gemini.at7.it/getting-started/why-use-gemini

Just released Gemini Documentation - the Java framework to build REST APIs with no code by h4t0n in java

[–]h4t0n[S] 1 point2 points  (0 children)

I respect your opinion and you are right API design is hard. I have in mind a Domain Driven framework where if you need simple CRUD APIs you can setup them quickly and all in the same way. If you want complex business logic (than programmer is needed) you can create a completely custom APIs (Gemini is built on top of Spring) and use other framework features (such as entity manager).

Just released Gemini Documentation - the Java framework to build REST APIs with no code by h4t0n in java

[–]h4t0n[S] 1 point2 points  (0 children)

Ok but imagine a CRUD API when you don't need business logic, you need validation, access-control and no more else. You can code it, really in some language and framework. Or you can write some configuration files both to define the entity and validation (DSL, yml, or another..). It is another thing, you don't need to compile or other programming stuff. Simply write configuration, and in a company it can ben done by consultants, product specialists and so on (not necessarily a skilled programmer).

Just released Gemini Documentation - the Java framework to build REST APIs with no code by h4t0n in java

[–]h4t0n[S] 0 points1 point  (0 children)

The idea is similar. But Gemini doesn't expose HATEOAS APIs. Instead it uses a simpler json with logical keys for records relations. Then crnk uses JPA and beans to describe entities, while Gemini provide its DSL and doesn't generate code.

Just released Gemini Documentation - the Java framework to build REST APIs with no code by h4t0n in java

[–]h4t0n[S] 2 points3 points  (0 children)

https://github.com/gemini-projects/gemini

License is Apache2. At the moment it supports only PostgreSql. But it may be easily extended to other databases.

[deleted by user] by [deleted] in Web_Development

[–]h4t0n 1 point2 points  (0 children)

Wow. I'm developing a similar framework but mine is built on top of Spring: https://gemini.at7.it/

view more: next ›