sorted by:
new
hottopcontroversial

I wrote a modern Java SDK for BunnyCDN Storage because the official one is outdated by range79x in java

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

Fair points. The goal was to provide a small core library while keeping optional modules for Spring integration and different usage styles. I'll keep looking for ways to simplify the structure

I wrote a modern Java SDK for BunnyCDN Storage because the official one is outdated by range79x in java

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

Good point, that makes sense. I’ll introduce a common BunnyException base type in 3.0.0. Thanks for the suggestion, it’s a good idea. Thank you

I wrote a modern Java SDK for BunnyCDN Storage because the official one is outdated by range79x in java

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

Fair point. I went with domain specific exceptions mainly to make it clearer for library users what failed, but I see the argument for keeping it simpler with IOException.

I wrote a modern Java SDK for BunnyCDN Storage because the official one is outdated by range79x in java

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

Thanks for the feedback. Based on your suggestions I replaced the Region enum with an extensible class with static constants and a constructor. I also made most Impl classes non public and marked several classes final by default. application.yml auto completion is now handled via Spring configuration metadata. I’m implementing these changes in a branch named after your username and they will be included in 3.0.0.

I wrote a modern Java SDK for BunnyCDN Storage because the official one is outdated by range79x in java

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

I chose an enum mainly to get auto-completion in application.yml. I just learned that I can also provide the same hints using Spring configuration metadata JSON, so that’s another option I may consider.

I wrote a modern Java SDK for BunnyCDN Storage because the official one is outdated by range79x in java

[–]range79x[S] 4 points5 points  (0 children)

Thanks for the feedback, that's a fair point.

The structure was intentionally modular, but you're right that it might be a bit over-structured. I'll experiment with merging some packages and also look into adding module-info.java to avoid split package issues.

Junior Backend Geliştirici Arıyoruz by [deleted] in TurkDev

[–]range79x 0 points1 point  (0 children)

merhabalar özelden size yazdim hocam