Activities of "improwise"

[maliming] said: hi

We will show some in the console if this endpoint is wrong.

Thanks.

Hi,

Is this something that will be changed in the future as at least we didn't see anything in console?

Also, how com this isn't working as we have not changed the URLs or paths as I know and they should be relative to the baseURLwhich seem to be working?

Thanks, will look into that. But how come this isn't, at least what we have found, more clearly logged/indicated?

Thanks

Can we PLEASE fix this damn service bot closing unresolved tickets?

Actually, I thought so to but turns out they properties are actually included all the way, at least with the Angular UI we are using. All you need to do is to fix the last step to actually have them show up. This is at least true for the list (GetList), have not looked if they are included for Get(xxx) as well.

    <ngx-datatable-column name="{{ '::CreationTime' | abpLocalization }}" prop="measurementAssignment.creationTime" >
      <ng-template let-row="row" ngx-datatable-cell-template>
        {{ row.xxx?.creationTime | shortDateTime }}
      </ng-template>
    </ngx-datatable-column>

Update, seems like this properties are actually included so what would be needed is more an option i ABP Suite to actually control if they are shown etc.

Perhaps some middle ground would be to include the most frequently used base properties in DTOs etc but not render them automatically in UI etc.

Could you implement this using the Extended classes etc so that even if you have to do it manually, they would still survive regenerations in ABP suite etc?

All this can of course be solved today, just as you could manually do anything ABP Suite does, but the goal here is of course not having to unless you want something more specific than to include some base properties.

Needs a human

If you are using ABP Suite to generate UI etc, it seems like properties of base classes are never included in DTOs etc and there AFAIK, there is no option to do so either. Assuming it isn't there, this is something that ABP should consider including. This could be either that you can just select the built in properties for addition to the properties you add manually, or that you could perhaps manually add a property with the same name as a built in one, which would then make the built in one be included etc.

To make this a bit more obvious what we are looking for, assume a simple use case like we want to display the CreatedTime of a new record/object in the UI. This property probably exists in all base classes for entities, but to actually do it now, I believe you have to add it manually in all layers. If I am wrong, please let me know how to do it.

Thanks.

[maliming] said: I haven't encountered this issue before, so I need to reproduce it. Right now, I haven't even seen any logs, so I really have no idea where the issue is.

Do you have any ideas how I can reproduce it?

Thanks.

The lack of logs is kind of the problem here, especially considering that besides the error dialog, we have not really seen anything being broken :)

Since there seem to be no logging behind whatever is triggering the error message, is there perhaps a way that we could temporarily modify some code just to get a feeling for what's triggering it?

Seems to be related to Angular app being in Azure, as just calling the backend in Azure from the Angular app running locally does not produce this error message.

[maliming] said: hi

Can you share the requests HAR file first?

https://abp.io/support/questions/8622/How-to-enable-Debug-logs-for-troubleshoot-problems#answer-3a1a1c4b-691e-3403-98b9-5f23fa024759

liming.ma@volosoft.com

Thanks.

Distributing HAR files will have to be considered as they contain a lot of information we might not want to share.

Is there no way of at least getting an idea from logs etc what is triggering this error message? I assume it cant just magically appear on its own, there has be be some ABP logic somewhere catching something and then creating the message?