Hello,
Is it possible for you to share the response of /api/abp/api-definition?includeTypes=true?
Hello,
At the moment, there is no API provided to add another tab in that page. We will take this as a feature request and put it in our roadmap.
Instead, you can replace the entire page with eIdentityComponents.OrganizationUnits which can be imported as
import { eIdentityComponents } from @volo/abp.ng.identity.
You can refer to the docs about how to use that key to replace the OrganizationUnits component.
What I meant by "The best way to ensure displayed time consistency across different timezones is to return this value as a string from the backend, so the client timezone won't change how it is displayed." is to send date objects as strings across platforms and convert it in locally. If you send a timestamp, when it is converted to a local timezone, it'll differ.
For example; my timezone is GMT+3 and the timestamp of the date '19/10/2021 00:00:00' is 1634590800. If I send this to a backend with timezone GMT+1, it will be converted to '18/10/2021 23:00:00', instead, I should just send '19/10/2021 00:00:00' as a string and let the backend convert it to a date object with its own timezone. The same goes for the frontend as well. The only thing that frontend and backend needs to shake on is the datetime format, then they can convert strings to date objects on their own.
Would that work out for you?
Hello,
The best way to ensure displayed time consistency across different timezones is to return this value as a string from the backend, so the client timezone won't change how it is displayed.
Regarding your other question; internally we use the date picker component of ng-bootstrap which allows us to provide our own DateTimeAdapter. However, as far as I can see that you use another library that may have a similar option.
Here is how we achieve such a thing with NgbDatePicker
Here is DateTimeAdapter
And here is how we utilize it in a component
Hello
Thanks for the detailed example, we will investigate it closely.
Hello @linch,
I've just tried with version 4.4.2 and the angular UI got generated just fine. What kind of problem did you encounter?
Hello,
You can follow the instructions in this document to utilize the @abp/ng.account package.
Hello,
LookupTypeaheadComponent currently does not support such inputs. However, you can utilize the typeahead component of ng-bootstrap which the abp-lookup-typeahead component already uses under the hood.
Cannot add property _userName, object is not extensible
Hello,
The error seems to be related to this
Our extensible table adds some properties to the records of the table.
Do you call preventExtensions on the data?
Hello,
Thanks for reporting this issue. LeptonX is still in early alpha release and not production-ready. These kinds of bugs could occur.
We've created a repo to collect feedback and issues. For future problems, please open up an issue in that repo.
https://github.com/volosoft/lepton-theme
I'll create an issue for this scrolling problem. Please, feel free to report any bugs you've encountered within the repo above.