You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firebase Product: rules unit testing (auth, database, storage, etc)
[REQUIRED] Describe the problem
Steps to reproduce:
The method withSecurityRulesDisabled has no documentation. After digging, it turns out it does have documentation but it is missing a * to make it a JS doc, resulting in the doc being a comment. This means the api extractor never picks it up during build.
I would like to submit a PR to correct the issue. Also, I would like to include an example in the JS Doc to add clarity, since this method differs from the other context methods. I plan on including the following example.
I ran the script yarn docgen devsite and everything looks ok. Let me know if I'm missing anything or if I should use a different example. Here's a link to my proposed change.
The text was updated successfully, but these errors were encountered:
Thanks, feel free to make a PR. I was going to add a comment that there needs to be a - after @param callback - that line is outside of your change but your fix made this error visible.
[REQUIRED] Describe your environment
[REQUIRED] Describe the problem
Steps to reproduce:
The method withSecurityRulesDisabled has no documentation. After digging, it turns out it does have documentation but it is missing a * to make it a JS doc, resulting in the doc being a comment. This means the api extractor never picks it up during build.
Relevant Code:
The relevant line is here.
I would like to submit a PR to correct the issue. Also, I would like to include an example in the JS Doc to add clarity, since this method differs from the other context methods. I plan on including the following example.
I ran the script
yarn docgen devsite
and everything looks ok. Let me know if I'm missing anything or if I should use a different example.Here's a link to my proposed change.
The text was updated successfully, but these errors were encountered: