Nhipster blob entity generator issue front angular

[Toysurusse]

Overview of the issue

How to fix Blob front Angular view issue ?

Motivation for or Use Case

When you use nhipster entity generator with an angular front. Angular can't render the image of the blob after beeing storage in database.

Reproduce the error

use nhipster entity generator and you will have issue to view blob from backend.

Suggest a Fix

when the service nest get the blob image from the server, the image is convert in an buffer of hexadecimal. So I had to fix the service to add a converter hexaToString like the following function :
const blob = roadMap.image.toString('hex');
var result = '';
for (var i = 0; i < blob.length; i = i + 2) {
var decval = parseInt(blob.substr(i, 2), 16);
result = result + String.fromCharCode(decval);
}

JHipster Version(s)

last version

JHipster configuration

nhipster

[mraible]

@Toysurusse Can you please create a PR to fix this? I'll add a bug bounty for extra motivation. :)

[Toysurusse]

Ok perfect, I can prepare it for you. I've never worked on generator part of nhipster ; but I will make a PR and assign it to you when it should be done :)

Hi @Toysurusse, thanks for the interest!! But if the issue is related to NHipster server generator, could you open this in the related repo?
Otherwise if the issue is for angular client, the fix shuld be done in this repo (in case the code fix also the same issue for the official jhipster generator without nhipster generation).

@mraible could you remove the bug bounty tag here and add it in the new issue created in case of mirror issue?

Thanks a lot.

[mraible]

@amanganiello90 I removed. Please let me know if there's a new issue to add it to.

@Toysurusse your suggested PR is related only how the nodejs backend retrieve the blob? So the normal jhipster app does not have this issue? In this case you have to open an issue in the nhipster repository and fix the related template (if it is an angular template you have to overwrite the default jhipster adding the custom file in the https://github.com/jhipster/generator-jhipster-nodejs/tree/master/generators/client/templates/angular folder)

@Toysurusse any news? Could I help you? Is it a issue only for NHipster? if it is that, could you open a ticket in the related repo in order to support the process and the development? Thanks.

[github-actions]

This issue is stale because it has been open 30 days with no activity.
Our core developers tend to be more verbose on denying. If there is no negative comment, possibly this feature will be accepted.
We are accepting PRs 😃.
Comment or this will be closed in 7 days

@Toysurusse your suggested PR is related only how the nodejs backend retrieve the blob? So the normal jhipster app does not have this issue? In this case you have to open an issue in the nhipster repository and fix the related template (if it is an angular template you have to overwrite the default jhipster adding the custom file in the https://github.com/jhipster/generator-jhipster-nodejs/tree/master/generators/client/templates/angular folder)

@Toysurusse ??

[avdev4j]

@amanganiello90 I have moved this ticket to the proper repository ;)

Thanks.

[jlopezjuy]

Overview of the issue

How to fix Blob front Angular view issue ?

Motivation for or Use Case

When you use nhipster entity generator with an angular front. Angular can't render the image of the blob after beeing storage in database.

Reproduce the error

use nhipster entity generator and you will have issue to view blob from backend.

Suggest a Fix

when the service nest get the blob image from the server, the image is convert in an buffer of hexadecimal. So I had to fix the service to add a converter hexaToString like the following function :
const blob = roadMap.image.toString('hex');
var result = '';
for (var i = 0; i < blob.length; i = i + 2) {
var decval = parseInt(blob.substr(i, 2), 16);
result = result + String.fromCharCode(decval);
}

JHipster Version(s)

last version

JHipster configuration

nhipster

I have same error, because nest with typeor get the blob file from database on BUFFER type. and this sugested fix only work on determinates files. im using files.

@column({ type: 'blob', name: 'documento', nullable: true })
documento: any;

@column({ name: 'documento_content_type', nullable: true })
documentoContentType: string;

on mi service:

const blob = gestion.documento.toString('hex');
var result = '';
for (var i = 0; i < blob.length; i = i + 2) {
var decval = parseInt(blob.substr(i, 2), 16);
result = result + String.fromCharCode(decval);
}
console.log(result);
gestion.documento = result;
docuFiltered.push(gestion);

@jlopezjuy thanks for the response, but I don't understand very well your message. You are saying, that the fix suggested do not resolve the angular blob issue?