-
Notifications
You must be signed in to change notification settings - Fork 7
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
Setup docs app #44
Setup docs app #44
Conversation
|
56b0ba6
to
f935bdd
Compare
@NullVoxPopuli this message seems to suggest we need to create a new project for this? Do you have the permissions, I don't have any cloudflare access on behalf of CS, right? |
I just made it 🎉
Right, we can get you added if you want (UX has its own cloudflare account). But for this kind of setup you also would need to be a GitHub org admin. :( |
f935bdd
to
d4372e3
Compare
Preview URLsEnv: preview |
d5ad508
to
d132285
Compare
persist-credentials: false | ||
- uses: ./.github/actions/pnpm | ||
- run: pnpm build | ||
# - uses: ./.github/actions/download-built-package |
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.
Can this be removed since we have the build run
above+below?
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.
The other jobs also still have this. We should clean up all of this of course, when we have the final solution, which I hope #52 will bring!
.github/workflows/ci.yml
Outdated
persist-credentials: false | ||
- uses: ./.github/actions/pnpm | ||
- run: pnpm build | ||
# - uses: ./.github/actions/download-built-package |
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.
Same question here as above
.github/workflows/ci.yml
Outdated
## Preview URLs | ||
Env: ${{ needs.PublishDocstoCloudflarePages.outputs.env }} | ||
Docs: ${{ needs.PublishDocstoCloudflarePages.outputs.url }} | ||
# # api docs: ${{ needs.PublishDocstoCloudflarePages.outputs.url }}/api/modules.html |
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.
I should maybe do this as well in toucan-core, as we don't have api docs yet!
</div> | ||
</template>; | ||
|
||
export default FeatureCard; |
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.
Maybe we can/should move these over to oss-docs
eventually? (Not part of this PR, obvs, low priority!)
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.
Yeah, I think this was even mentioned somewhere, in a comment or so. Just vaguely remember...
"highlight.js": "^11.6.0", | ||
"highlightjs-glimmer": "^1.4.1", | ||
"tracked-built-ins": "^3.1.0" | ||
} |
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.
Do you need the dependenciesMeta
here as well? E.g.,:
"dependenciesMeta": {
"ember-headless-form": {
"injected": true
}
}
(https://github.com/CrowdStrike/ember-toucan-core/blob/main/docs-app/package.json#L134)
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.
It seems like it was working without it based on what I read from a previous PR (let me dig it up)...but then how come we need it in other packages?? (don't feel the need to answer this if it's going to take a lot of investigation btw, just curious)
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.
Update, yeah you are right it was added over here: https://github.com/CrowdStrike/ember-headless-form/pull/49/files#diff-b03f4acb30e04ceb12a40763ef649759b3f632df2357bcec14fab6dd29ebbfb4R124 in the test app
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.
It wasn't needed as I wasn't really using the addon in the docs app yet. But yes, your are right, we should do that here also - and I just did that, to prevent any more foot guns due to this unfortunate issue.
// Additional setup for unit tests can be done here. | ||
} | ||
|
||
export { setupApplicationTest, setupRenderingTest, setupTest }; |
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.
Totally non-blocking quesiton: We have all of the same in toucan-core
under docs-app/tests
, but I'm curious if it makes sense for our docs-apps to even have the tests/
directory? We normally use the test-app
for testing, so just curious on thoughts around this.
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.
over time docs may have demos complex enough where you want them tested
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.
Ah, that makes sense 👍
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.
Yeah, and I would also like to add even just a very simple smoke test for the docs app, mainly checking that the build does not blow up, and at least something is rendered. This has proven to be useful in other projects like ember-bootstrap, to make sure that e.g. automated renovate updates don't accidentally the docs app!
'use strict'; | ||
|
||
module.exports = { | ||
plugins: ['prettier-plugin-ember-template-tag'], |
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.
!! Should we be using this in our other packages? Does it format everything in between <template>
tags (is this what it does?)
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.
We have this already in the test-app for example. It makes prettier even understand the existence of <template>
, otherwise it wouldn't be able to parse the file (as it's not valid JS/TS). And yes, it does also format everything inside of the template!
|
||
## Running / Development | ||
|
||
- `ember serve` |
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.
Question...are we really running ember serve
or is it pnpm start
? Or should updating this README
be in a followup?
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.
they are equiv 🎉
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.
This was copy-paste, and yes, currently there is no difference. However, should we start to add turbo also to scripts in the workspace, including start
, then it would start to matter!
Co-authored-by: Tony Ward <8069555+ynotdraw@users.noreply.github.com>
7c1bb48
to
03b88ac
Compare
03b88ac
to
c324e7a
Compare
@NullVoxPopuli I took the freedom to refactor the docs CD workflow a bit, in this commit. Previously we had a separate Btw, that |
This is only the boilerplate of the docs app, copied from ember-toucan-core, and enabling CI/CD. Writing the actual documentation will follow in separate PR(s).