/**
 * Activity Details Utilities
 * Helper functions for activity details components
 */
import type { StudentActivityStatus, StatusBadgeConfig } from '../types/activityDetails';
/**
 * Get status badge configuration
 * @param status - Student activity status
 * @returns Status badge configuration with label and colors
 */
export declare const getStatusBadgeConfig: (status: StudentActivityStatus) => StatusBadgeConfig;
/**
 * Format time spent in seconds to HH:MM:SS
 * @param seconds - Time in seconds
 * @returns Formatted time string in HH:MM:SS format
 */
export declare const formatTimeSpent: (seconds: number) => string;
/**
 * Format question numbers to display
 * @param numbers - Array of question numbers (1-indexed from API)
 * @returns Formatted string with question numbers (padded)
 */
export declare const formatQuestionNumbers: (numbers: number[]) => string;
/**
 * Format date string to Brazilian format (DD/MM/YYYY)
 * @param dateString - ISO date string
 * @returns Formatted date string
 */
export declare const formatDateToBrazilian: (dateString: string) => string;
/**
 * Format an ACTIVITY date (start/deadline) to Brazilian DD/MM/YYYY in LOCAL
 * time. Activity dates are stored in local-time terms — a deadline "ends on
 * day X" is persisted as 23:59 local (e.g. 02:59Z of day X+1). Formatting in
 * UTC (see formatDateToBrazilian) would show the day after for such values,
 * disagreeing with the calendar dots and the activities list. Use this for
 * activity start/final dates so all three stay on the same local day.
 *
 * NOTE: this is intentionally separate from formatDateToBrazilian, which is
 * also used for lesson dates stored as UTC midnight ('2024-01-01T00:00:00Z')
 * where the UTC day is the intended one.
 * @param dateString - ISO date string
 * @returns Formatted date string (DD/MM/YYYY) in local time
 */
export declare const formatActivityDateToBrazilian: (dateString: string) => string;
//# sourceMappingURL=activityDetailsUtils.d.ts.map