BrowserDownloadsView 1.45 for ios instal

Do not include 'Fixed PR comments', merge commits, or other 'temporary' commits in pull requests.

Follow-up commits for any review comments should be squashed.

If a commit requires another commit to build properly, those commits should be squashed.If a commit contains multiple unrelated changes, those changes should be split into separate commits. Each commit should have a single clear purpose.We recommend enabling the 'Automatically trim trailing whitespace' and keeping 'Including whitespace-only lines' deselected in Xcode (under Text Editing).New code should not contain any trailing whitespace.Swift code should generally follow the conventions listed at.PRs will be squashed and merged, so it is important to keep PRs focused on specific tasks.In the unlikely and rare situation that a PR fixing multiple, related issues separate issue numbers with a comma:įix #159, Fix #160: Removed whitepsace for + button on right-side panel.Add any additional information regarding the PR in the description.Ref #102: Fixed type on Face ID usage description. Please use the following formats in your PR titles:įix #102: Added Face ID usage description to plist.If a bug corresponding to the fix does not yet exist, please file it.

All pull requests must be associated with a specific GitHub issue.Instructions on building and updating this code can be found here Contributor guidelines Creating a pull request Many features in iOS (sync, ads, wallet, etc.) are powered by shared code in brave-core. Sudo ln -s $(which node ) /usr/local/bin/node Sudo ln -s $(which npm ) /usr/local/bin/npm

BrowserDownloadsView 1.45 for ios instal