-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
Create dev build infrastructure #4223
Comments
@handrews How luxurious do you want it to be? The simplest solution would be to add a script A nicer experience would be to start a tiny express server via I have copy templates for both approaches lying around 😎 |
@ralfhandl I'm perfectly happy with the simple version (and would be more likely to use it TBH because all of my dev tools tend to be the lowest-tech that works for me). But if you want to do the more complicated thing I'm not going to stop you. Although... express seems like a bit dependency to add, and I'd kind-of like to be able to just build and look at the HTML without running a server. I guess just make sure I don't have to understand express at all to use the build system. |
@handrews Please check |
I had a check fail on #4188 on
v3.2-dev
and realized that there's no way to build without copying things over to the publish location (and even then something went weird when it was trying to build the old versions b/c the dev branches aren't set up for that).We should be able to build just
src/oas.md
for testing purposes ondev
and all branches derived fromdev
.This change should go into
dev
and be merged/cherry-picked out from there.If Arazzo and Overlay are going to use the same system, this might also be a good time to start building a shared system instead of continuing to patch things in triplicate.
src/oas.md
src
src
upon pushsrc/oas.md
upon pushsrc/oas.md
The text was updated successfully, but these errors were encountered: