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

Refactor imports #157

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open

Refactor imports #157

wants to merge 6 commits into from

Conversation

thisisjofrank
Copy link
Contributor

No description provided.

Copy link
Member

@arnauorriols arnauorriols left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Member

Choose a reason for hiding this comment

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

Why rename this directory?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

So the components are all collated rather than knocking around in the root. Separate them from the configuration files etc

Copy link
Member

Choose a reason for hiding this comment

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

Seems good to move source under src/ but the rename is testdata/posts/fifth.mdcontent/posts/fifth.md, presumably calling it content instead of testdata has no impact on where the components are located. testdata is intentionally named for test fixtures.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ah sorry, thought I saw the comment attached to the above file.
My thought for the rename was that it was a better example of a sensible file name, that users can 'clone and go', But not a hill I would die on, happy to change it back.

Copy link
Member

Choose a reason for hiding this comment

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

I'd suggest undoing the content change and intead move testdata to src/testdata

Comment on lines +16 to +21
"@denoland/htm": "https://deno.land/x/[email protected]/mod.ts",
"@denoland/htm/plugins/color-scheme": "https://deno.land/x/[email protected]/plugins/color-scheme.ts",
"@denoland/htm/plugins/unocss": "https://deno.land/x/[email protected]/plugins/unocss.ts",
"@denoland/g_a": "https://deno.land/x/[email protected]/mod.ts",
"@githubcontent/kt3k/callsites": "https://raw.githubusercontent.com/kt3k/callsites/v1.0.0/mod.ts",
"@outdated/std-http": "https://deno.land/[email protected]/http/mod.ts",
Copy link
Member

Choose a reason for hiding this comment

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

It seems weird (but not technically wrong) to give these fake scope names

"tasks": {
"dev": "deno run --allow-net --allow-read --allow-env=NODE_DEBUG,NO_COLOR,FORCE_COLOR,TERM --watch --no-check ./content/main.tsx --dev",
"test": "deno test --allow-net --allow-read --allow-env=NODE_DEBUG,NO_COLOR,FORCE_COLOR,TERM --no-check=remote",
"serve": "deno run --allow-net --allow-read --allow-env --no-check ./content/main.tsx"
Copy link
Member

Choose a reason for hiding this comment

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

--no-check and --no-check=remote are not needed here and above in modern deno

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.

3 participants