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.

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

docs: added info on bookmark return values for securityScopedBookmarks #17584

Merged
merged 1 commit into from Jan 23, 2020

Conversation

rr326
Copy link
Contributor

@rr326 rr326 commented Mar 27, 2019

Description of Change

Dialog.md does not document the expected return values for securityScopedBookmarks. You have to look through the code or old issues to understand how it is supposed to work.

This fixes that.

Checklist

Release Notes

Notes: Dialog.md does not document the expected return values for securityScopedBookmarks. You have to look through the code or old issues to understand how it is supposed to work.

@electron-cation electron-cation bot added the new-pr 🌱 PR opened in the last 24 hours label Mar 27, 2019
@welcome
Copy link

welcome bot commented Mar 27, 2019

💖 Thanks for opening this pull request! 💖

We use semantic commit messages to streamline the release process. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix.

Examples of commit messages with semantic prefixes:

  • fix: don't overwrite prevent_default if default wasn't prevented
  • feat: add app.isPackaged() method
  • docs: app.isDefaultProtocolClient is now available on Linux

Things that will help get your PR across the finish line:

  • Follow the JavaScript, C++, and Python coding style.
  • Run npm run lint locally to catch formatting errors earlier.
  • Document any user-facing changes you've made following the documentation styleguide.
  • Include tests when adding/changing behavior.
  • Include screenshots and animated GIFs whenever possible.

We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.

Copy link
Member

@MarshallOfSound MarshallOfSound left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we de-duplicate this information in a single place in this document and just link to it in these 3 places?

@rr326
Copy link
Contributor Author

rr326 commented Mar 28, 2019

That sounds good to me, but I was trying to match the existing convention where it seems to repeat the complete information for every API call.

I'm happy to make the change, but do we need to wait for any other confirmation from others, or do I just do it?

@electron-cation electron-cation bot removed the new-pr 🌱 PR opened in the last 24 hours label Mar 28, 2019
@codebytere
Copy link
Member

@rr326 you don't need confirmation, please make the change so we can move this forward!

@rr326
Copy link
Contributor Author

rr326 commented Jun 3, 2019

@codebytere Ok - I think I did this properly. I rebased off of the current version, made my changes, and then pushed to my branch. Please let me know if I did something incorrectly. (First pr.)

@codebytere
Copy link
Member

codebytere commented Jun 4, 2019

@rr326 looks like it's struggling a bit on the table linting:

AssertionError: We only support plain text, links, softbreaks, inline code, strong tags and paragraphs inside joinable tokens: expected 'table_open' to be one of [ Array(20) ]

if you've cloned Electron locally you can get a shorter feedback loop on this than waiting for CI by running npm run lint:docs on your branch!

@MarshallOfSound
Copy link
Member

To fix the above error the table can't be inside a method documentation block. It should be moved to it's own ## level block

@rr326
Copy link
Contributor Author

rr326 commented Jun 4, 2019

Ok - I think I've got it. Note - I noticed an error that one header (showSavedDialog) was incorrect, so I fixed that. It doesn't seem to warrant a whole separate PR process.

@codebytere
Copy link
Member

Last thing just looks like:
Trailing whitespace in: /home/builduser/project/src/electron/docs/api/dialog.md

@@ -154,7 +155,7 @@ dialog.showOpenDialog(mainWindow, {
})
```

### `dialog.showSaveDialog([browserWindow, ]options)`
### `dialog.showSaveDialogSync([browserWindow, ]options)`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah, this just got fixed yesterday actually! You'll see it on rebase

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry about that. Maybe I hadn't properly installed my fork. Now it's linting on its own and this one passes. Thanks for your patience.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank YOU for the contribution 🚀

@zcbenz
Copy link
Member

zcbenz commented Jan 23, 2020

I have rebase this branch on master.

@zcbenz zcbenz merged commit 1d58072 into electron:master Jan 23, 2020
@welcome
Copy link

welcome bot commented Jan 23, 2020

Congrats on merging your first pull request! 🎉🎉🎉

@release-clerk
Copy link

release-clerk bot commented Jan 23, 2020

Release Notes Persisted

Dialog.md does not document the expected return values for securityScopedBookmarks. You have to look through the code or old issues to understand how it is supposed to work.

@trop
Copy link
Contributor

trop bot commented Jan 23, 2020

I have automatically backported this PR to "7-1-x", please check out #21873

@trop
Copy link
Contributor

trop bot commented Jan 23, 2020

I have automatically backported this PR to "8-x-y", please check out #21874

@sofianguy sofianguy added this to Fixed in 7.1.11 in 7.2.x Feb 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
7.2.x
Fixed in 7.1.11
Development

Successfully merging this pull request may close these issues.

None yet

4 participants