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 :)
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.
We are seeing the exact same problem and investigating it. Not sure if it is actually a ABP problem yet or might have other causes as this project used to work last week. Did do some ABP Suite updates since then though that could have caused this.
Update, this seem to occur only with latest version of Chrome based on our testing, but works fine in Firefox and Edge. Seems like you can get it to work in Chrome by clearing cache, not sure what caused it though and if it might come back.
