Api#resourceByAssetID does not support same options as in documentation

Offen
  • Stimmt etwas nicht?
#357 2 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@adimiz1 arbeitet bereits daran.

Seit 06.2.2025.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

Bug report for Cloudinary Java SDK

Before proceeding, please update to latest version and test if the issue persists

Describe the bug in a sentence or two.

It seems that Api#resourceByAssetID does not support same parameters as describe in documentation.
In Cloudinary Api Docs . E.g image_metadata is described as supported option. Thus, i would expect that
cloudinary.api().resourceByAssetID(asset.asset_id(), Map.of("image_metadata", true)) would result in GET /v1_1/<client>/resources/<asset-id>?image_metadata=true. But actually it results in /v1_1/<client>/resources/<asset-id> without 'image_metadata' parameter.

Api#resourceByAssetID implementation does not match configuration options in documentation.

    public ApiResponse resourceByAssetID(String assetId, Map options) throws Exception {
        if (options == null) options = ObjectUtils.emptyMap();
        if(options.get("fields") != null) {
            options.put("fields", StringUtils.join(ObjectUtils.asArray(options.get("fields")), ","));
        }
        Map params = ObjectUtils.only(options, "tags", "context", "moderations", "fields");
        ApiResponse response = callApi(HttpMethod.GET, Arrays.asList("resources", assetId), params, options);
        return response;
    }

Since with simple curl the api responds with expected image metadata included my guess is that the java implementation is too restrictive.

Issue Type (Can be multiple)

[ ] Build - Can’t install or import the SDK
[ ] Performance - Performance issues
[x ] Behaviour - Functions aren’t working as expected (Such as generate URL)
[ ] Documentation - Inconsistency between the docs and behaviour
[ ] Other (Specify)

Steps to reproduce

… if applicable

Error screenshots or Stack Trace (if applicable)

…

Build System

[ ] Maven
[x ] Gradle
[ ] Other (Specify)

OS (Please specify version)

[ ] Windows
[ ] Linux
[ ] Mac
[ ] Other (specify)

Versions and Libraries (fill in the version numbers)

Cloudinary Java SDK version - 2.0.0
JVM (dev environment) - 0.0.0
JVM (production environment) - 0.0.0
Maven - 0.0.0 / N/A
Gradle - 0.0.0 / N/A

Repository

If possible, please provide a link to a reproducible repository that showcases the problem

Vorherrschende Sprache
Java
Sterne
176
Forks
113
Ø Merge
9 T. 20 Std.
Gemergte PRs (30 T.)
2

Entwicklungsumgebung

  • Kein Dockerfile und keine Docker-Compose-Datei
  • Hat eine Pull-Request-Vorlage
  • Kein Beitragsleitfaden

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus cloudinary/cloudinary_java

Alle Issues in cloudinary/cloudinary_java

Ähnliche Issues

Weitere Issues zu Java

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.