-
Notifications
You must be signed in to change notification settings - Fork 277
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
Generate API Documentation on build #334
Comments
Closed in #336 |
I'll reopen, as we will need to double check if this works when we merge development into master at some point .. Will probably need to push two commits, the first one will create the gh-pages branch, and then we will need to select the gh-pages branch in the settings as the branch for Github Pages . (currently it is set to master) Let me know if I missed something |
You can already prepare the repo to serve from You are right that we need to verify that it runs correctly. In my opinion though this feels more like a separate task as this task was to remove the |
true, will do that and put a note in the development notes |
As far as I can tell, the whole API Documentation can be generated with
npm run generateapidoc
. Therefore it should be considered build artifacts and not be comitted to git.Ideally,
npm run build
andnpm run dev
should build the apidoc automatically when executed.The text was updated successfully, but these errors were encountered: