Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

feat: use contextBridge in favour of requiring nodeIntegration #300

Merged
merged 4 commits into from
Jun 2, 2021
Merged

feat: use contextBridge in favour of requiring nodeIntegration #300

merged 4 commits into from
Jun 2, 2021

Commits on Mar 2, 2021

  1. feat: use contextBridge in favour of requiring nodeIntegration 

    Due to security concerns related to usage of nodeIntegration flag, according to best electron practices, renderer functions should be exposed with contextBridge. This PR does exactly that. It also changes a bit API to accomodate for this feature
    @matmalkowski
    matmalkowski committed Mar 2, 2021
    Configuration menu
    Copy the full SHA
    afab80a View commit details
    Browse the repository at this point in the history

  2. feat: fixing issues with test enviroment

    @matmalkowski
    matmalkowski committed Mar 2, 2021
    Configuration menu
    Copy the full SHA
    8afce8f View commit details
    Browse the repository at this point in the history

  3. fix: add missing preventDoubleInitialization() check

    @matmalkowski
    matmalkowski committed Mar 2, 2021
    Configuration menu
    Copy the full SHA
    debd89a View commit details
    Browse the repository at this point in the history

Commits on May 28, 2021

  1. change the scope of the contextBridge bindings to only expose high le… 

    …vel API
    @matmalkowski
    matmalkowski committed May 28, 2021
    Configuration menu
    Copy the full SHA
    5c1b94e View commit details
    Browse the repository at this point in the history