mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

docs: update dev docs atom -> shell (#22199)

Browse source
This commit is contained in:
Jeremy Apthorp 2020-02-16 16:47:22 -08:00 • committed by GitHub
parent f8c4be7caa
commit 360326ecad
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/development/debug-instructions-windows.md
View file

@ -48,7 +48,7 @@ still set breakpoints - Visual Studio will automatically figure out that the
source code matches the code running in the attached process and break source code matches the code running in the attached process and break
accordingly. accordingly.
Relevant code files can be found in `./atom/`. Relevant code files can be found in `./shell/`.
### Attaching ### Attaching

2
docs/development/debugging-instructions-macos.md
View file

@ -46,7 +46,7 @@ this basic introduction, let's assume that you're calling a command from JavaScr
that isn't behaving correctly - so you'd like to break on that command's C++ that isn't behaving correctly - so you'd like to break on that command's C++
counterpart inside the Electron source. counterpart inside the Electron source.
Relevant code files can be found in `./atom/`. Relevant code files can be found in `./shell/`.
Let's assume that you want to debug `app.setName()`, which is defined in `browser.cc` Let's assume that you want to debug `app.setName()`, which is defined in `browser.cc`
as `Browser::SetName()`. Set the breakpoint using the `breakpoint` command, specifying as `Browser::SetName()`. Set the breakpoint using the `breakpoint` command, specifying

2
docs/development/pull-requests.md
View file

@ -55,7 +55,7 @@ $ git checkout -b my-branch -t upstream/master
### Step 4: Code ### Step 4: Code
Most pull requests opened against the `electron/electron` repository include Most pull requests opened against the `electron/electron` repository include
changes to either the C/C++ code in the `atom/` folder, changes to either the C/C++ code in the `shell/` folder,
the JavaScript code in the `lib/` folder, the documentation in `docs/api/` the JavaScript code in the `lib/` folder, the documentation in `docs/api/`
or tests in the `spec/` folder. or tests in the `spec/` folder.