fix: redacted log - #50
Merged
Merged
Conversation
…e to the bundle A packaged copy opens Default apps on its own page through its AUMID; the registeredAppUser name only exists for the installer copy, so the Store copy landed on the generic list. A UserChoice whose class runs a program that is gone no longer counts as default. Settings no longer takes the registration from another copy that still exists: reconcile follows a moved install, the wrong binary or a scheme key that disagrees, and leaves the rest alone. The resident keeps the detected browsers for thirty seconds instead of walking the registry and every Local State on each click; catalogue moves to detected.rs and the shell's main.rs shrinks. The window's notices come from what the bundle really holds, read from a sourcemapped vite build, so argparse drops out; the check now also runs when the window's sources change. The README stops promising to unwrap the Edge scheme.
…n share A rules file that could not be read, or a rule whose browser would not start, used to fall through to the picker without a word. Now a notice says what failed, with no Undo, and the picker still opens for the link. Every such failure, and a rule that could not be saved or forgotten, writes one line to errors.log in the data folder: UTC time, what failed and why. Before it is written an address with :// is cut to scheme, host and port, one without is dropped, the home folder becomes ~ and any other Users or home owner becomes an ellipsis. The latest 200 lines are kept, written through a rename. Nothing is sent: Save report ends with them, already redacted. The notice code moves to notice.rs and the report command to about.rs, so both files under the line ceiling shrink. PRIVACY, SECURITY and the README say what the log holds and that it leaves only when shared.
rgdevment
changed the title
rgdevment
changed the title
…ccount name is hidden whole LOCALAPPDATA and APPDATA were replaced by ~ too, so a rules file under the profile read as ~\LinkUnbound\rules.json, a folder that does not exist; only USERPROFILE and HOME stand for ~ now. The owner of a Users or home path was cut at the first space, so "Ana Maria" left "Maria" in the line; it now ends at a slash or a quote.
…ter an account name With the home at C:\Users\Ana, C:\Users\Anabel came out as ~bel; the home is now replaced only where its path ends, and the other account is hidden as any other. An account name with nothing but text after it swallowed the rest of the line, reason included; it now ends at a colon, a bracket or a comma too, trailing spaces left outside.
…picker A link whose rule failed while the picker was open for another one showed its notice without returning the keyboard, so the digits being typed into the picker were lost. It now does what a rule's own notice already did.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.