We’re on ABP Framework v10 with the Angular UI and use the abpUtcToLocal pipe to show datetimes in the tenant timezone (e.g. {{ value | abpUtcToLocal: 'datetime' }}). The tenant timezone is set to US/Pacific (IANA). Clock kind on the server is UTC
What we saw After daylight saving started on March 10 in the U.S., all displayed times were one hour behind the correct local time. Before DST they were correct.
What we found In @abp/ng.core, UtcToLocalPipe calls TimeService.formatDateWithStandardOffset(). That method uses the timezone’s standard (January) offset only and does not apply DST rules, so Pacific stays at UTC−8 instead of switching to UTC−7 in summer. TimeService also has a DST‑aware format() that uses Luxon with the full IANA zone; the pipe doesn’t use it.
Question:
Was the use of formatDateWithStandardOffset (and thus “no DST”) intentional? If so, is there a recommended way to get DST‑aware UTC‑to‑local display with the existing pipe or services? Would you consider changing the pipe to use the DST‑aware formatting by default (or adding an option), so that a setting like “US/Pacific” behaves like users expect after DST starts?
Workaround we used We provided a custom TimeService that overrides formatDateWithStandardOffset() to call this.format(value, format, zone) instead, so the pipe’s behavior becomes DST‑aware without changing templates. We’re happy to share that approach if it’s useful for the docs or a sample.
import { Injectable } from '@angular/core';
import { TimeService } from '@abp/ng.core';
/**
* Uses DST-aware conversion for UTC-to-local display.
* ABP's UtcToLocalPipe calls formatDateWithStandardOffset (standard offset only);
* we override to use format() so daylight saving time is applied.
*/
@Injectable({ providedIn: 'root' })
export class ToadTimeService extends TimeService {
override formatDateWithStandardOffset(
value: string | Date,
format = 'ff',
zone?: string
): string {
return this.format(value, format, zone ?? 'local');
}
}
1 Answer(s)
-
0
Hello,
Thank you for yor kind interest and contribution. As you have also explained the server treats tenant timezone as DST‑aware. However, The Angular pipe is the only place that forces “standard offset only” for display when an IANA zone like
US/Pacificis set intentionally.So, changing the pipe to use DST‑aware formatting by default (e.g. by calling
format()instead offormatDateWithStandardOffset()) would align with the server and with user expectations for IANA zones and would fix the “one hour behind after DST” issue.You can also consider contributing a backward-compatible change (e.g. an optional parameter on
abpUtcToLocalto use DST-aware formatting, or a dedicated DST-aware pipe). You can find details in this contribution guide.You can let us know if you need further assistance. Thank you for your cooperation.
