-
Notifications
You must be signed in to change notification settings - Fork 189
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
Markdown results: Change folder structure and add sample data for problem query #1303
Conversation
import { generateMarkdown } from '../../../../src/remote-queries/remote-queries-markdown-generation'; | ||
|
||
describe('markdown generation', async function() { | ||
it('for path-problem-query: should generate markdown file for each repo with results', async function() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor: It might make sense to use nested describe
blocks. So, here you would change to:
it('for path-problem-query: should generate markdown file for each repo with results', async function() { | |
describe('for path-problem-query', () => { | |
it('should generate markdown file for each repo with results', async function() { |
And then fix indenting below. Same with the second test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor suggestion, which you can take or leave.
To be clear, though. This PR doesn't contain any behavioural changes, only restructures the tests?
5f08a29
to
50c9e16
Compare
Thanks for the tidy-up tip!
Correct! I'll have some more substantial changes in a follow-up PR 😄 |
(Based on #1302)
This PR adds sample data for a (non-path) problem query. Currently these are rendered the same, but I'll add special rendering for paths in a follow-up PR! See internal issue 👀
Checklist
N/A - internal only
ready-for-doc-review
label there.