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

Pipeline uses JSDOCS now to generate files for js files #58

Merged
merged 35 commits into from
Jun 10, 2023

Conversation

bsalvania
Copy link
Contributor

@bsalvania bsalvania commented Jun 9, 2023

I think I got JSDOCS to work with our pipeline. I renamed all the javascript files to match what website they are for and moved them to a common folder (assets/scripts). It generates documentation for the js files in assets/scripts and outputs them into the JSDOCS folder.

Also for JSDOCS to produce documentation, the js files need JSDOC comments so add them to your js files if you haven't already.

close #50

@SheepTester
Copy link
Member

hmm it'd be nice if we didn't have to move the JS files out of the source folder

@@ -8,6 +8,7 @@
"ecmaVersion": "latest",
"sourceType": "module"
},
"ignorePatterns": ["/JSDOCS/scripts"],
Copy link
Member

Choose a reason for hiding this comment

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

could probably ignore the entirety of JSDOCS but this is fine too

@SheepTester SheepTester merged commit 4b17915 into main Jun 10, 2023
@SheepTester SheepTester deleted the jsdocs-pipeline branch June 10, 2023 05:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CI/CD: JSDOCS
4 participants