[packageInfo] Change the abbreviation of "ft" to "File Time"

Open Beginner friendly
#600 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
python

Research direction

Find the script 'packageInfo' that parses packages.xml and generates the HTML report. Look for where column names like 'ut' are mapped to 'Update Time' and add a mapping for 'ft' to 'File Time'. To add hover tooltips, examine the report template to see how column headers are rendered and add title attributes or similar. Test by running the script on a sample packages.xml and checking the generated report.

Written by the indexing model from the issue text.

Description

Hello,

Ran multiple scripts but I'm quite sure the script "packageInfo" (which parses "packages.xml") is the one which results in the "Installed Apps" > "Packages" in the HTML-report.

In the actual packages.xml you have the following tags / fields:
"ft" which the report doesn't expand on and simply names "ft"
"ut" which the report renames to "Update Time"

In my case I didn't have the following tags / fields:
"it" = Install Time (which in my report is blank)

I would like that the report rename the "ft" column to "File Time" since according to ChatGPT:
"ft = File Time (last modification time of the APK in seconds since epoch)."

What also would be nice would be an icon such as an "(i)" next to each column for:
File Time
Install Time
Update Time
Install Orginator
Installer
etc.
which explains further what each column is for, ex:

File Time (i)

When you hover over (i) you get:
"File Time (last modification time of the APK in seconds since epoch)."

Thank you for your work, really helps out!

Best Regards

Dominant language
Python
Stars
924
Forks
246
Avg merge
5h 18m
Merged PRs (30d)
234

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from abrignoni/ALEAPP

All issues in abrignoni/ALEAPP

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.