BTW, the name of this thread should probably change now in 2025.
In ABP Suite when creating properties for Entities, it would be nice if you besides "Name" could enter an optional "UI name" or something like that, that would be used in the generated UI instead of Name.
For example, if you create a property "HomepageUrl" for a Company entity, you would probably want that to show up as "Homepage:" rather than "HomepageUrl:" in UI.
We do not typically close tickets unless they are fully resolved or inactive for some time. We understand the issue you are facing and are actively working on a fix to prevent this from happening again. Thanks for your patience.
The problem seems to be an overzealous bot with really poor patience that decides to close even unresolved ticket way too early.
When adding the Public website option, the run-docker.ps1 does not seem to work
! coin-web-public Warning manifest for improwise/coin-web-public:latest not found: manifest unknown: manifest unknown
[coin-web-public 2/3] COPY bin/Release/net9.0/publish/ app/:
failed to solve: failed to compute cache key: failed to calculate checksum of ref redacted::redacted: "/bin/Release/net9.0/publish": not found
Please fix the problem that tickets get closed even though you just reopened them
Thanks you for a quick response to this and also the created ticket on GitHub. And yes, I fully understand that keeping docs updated is somewhat of a PIA.
Since we seem to agree about the need for this, I guess this ticket should be refunded :)
Sure. I have refunded your ticket :)
Thanks.
Please do not share our account specific info here even though it isn't exactly sensitive information :)
Removed 👍
Thanks!
Thanks you for a quick response to this and also the created ticket on GitHub. And yes, I fully understand that keeping docs updated is somewhat of a PIA.
Since we seem to agree about the need for this, I guess this ticket should be refunded :)
Sure. I have refunded your ticket :)
Thanks.
Please do not share our account specific info here even though it isn't exactly sensitive information :)
Hi, thanks for your suggestion. As you said, some parts of the documentation might be outdated. Therefore, we need to revise all of our Angular documents from that perspective. I have created an issue for that and assigned it to a member of our angular team, which you can follow the progress from https://github.com/abpframework/abp/issues/22092.
We are revising and updating our documents whenever possible but as you know it's really hard to maintain such a big documentation system. Thanks for your understanding, in advance.
Best regards.
Thanks you for a quick response to this and also the created ticket on GitHub. And yes, I fully understand that keeping docs updated is somewhat of a PIA.
Since we seem to agree about the need for this, I guess this ticket should be refunded :)
The documentation at https://abp.io/docs/latest/framework/ui/angular is good in general but it is now a bit out of date, both regarding Angular itself (like still linking to old angular.io rather than angular.dev, older versions of Angular etc) and also about the Angular implementation/template in ABP. It needs to be updated overall.
Also the Angular template itself should be probably be updated to use best practices according to newer versions of Angular but there are perhaps different opinions regarding the usage of NgModule etc. At least the Angular team does not recommend using it anymore
"IMPORTANT: The Angular team recommends using standalone components instead of NgModule for all new code. Use this guide to understand existing code built with @NgModule."
Updating the docs are probably of higher importance right now.
Thanks.
It seems when using the Angular UI and creating Navigation properties, ABP Suite tries to invent the type "Guid" in Angular/Typescript even though that does not exist (at least not by default). If you change it to string it will work both development time and run time it seems.
