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

Update docs to account for recent changes #808

Merged
merged 72 commits into from
Nov 11, 2022
Merged

Conversation

sodic
Copy link
Contributor

@sodic sodic commented Nov 9, 2022

Updates the docs together with the Todo example apps to account for recent changes in the project structure, covers documentation differences for:

sodic and others added 30 commits October 12, 2022 15:28
Co-authored-by: Shayne Czyzewski <[email protected]>
Co-authored-by: Martin Šošić <[email protected]>
@sodic sodic marked this pull request as ready for review November 9, 2022 12:41
@sodic sodic force-pushed the filip-update-docs-new-structure branch from 8eb1c76 to 313d2b7 Compare November 9, 2022 12:46
@sodic sodic changed the title Update docs and example apps to account for recent changes Update docs to account for recent changes Nov 9, 2022
Copy link
Contributor

@shayneczyzewski shayneczyzewski left a comment

Choose a reason for hiding this comment

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

Awesome attention to detail here, @sodic. I know it was a lot of effort to get all this updated. Nice job!

One page I noticed that still references @ext is the main page web/src/pages/index.js, as does one line in features.md (js title="ext/myClientSetupCode.js")

I tried to drop in suggested edits where I thought they made sense, but even my eyes could not be trusted near the end of reviewing it all haha :D It all becomes very sneaky/subtle, so take them with a grain of salt. I will do another review with fresh eyes after you have a chance to check out the ideas here. 👍🏻

web/docs/tutorials/todo-app/creating-new-project.md Outdated Show resolved Hide resolved
├── .gitignore
├── main.wasp # Our wasp code goes here.
├── src
│   ├── client # Our external client code (JS/CSS/HTML) goes here.
Copy link
Contributor

Choose a reason for hiding this comment

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

Even though this convention was here before, and you explained it well below, I still find "Our external code" a bit confusing. On these three lines, is it ok if we just say "Your client code", etc.?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Much better, thanks!

@@ -11,13 +11,19 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
To enable support for Tailwind in your Wasp project, you simply need to add two config files (`tailwind.config.js` and `postcss.config.js`) to the root directory. When they are present, Wasp will add the necessary NPM dependencies and copy your config files into the generated project output. You can then start adding [Tailwind CSS directives](https://tailwindcss.com/docs/functions-and-directives#directives) to your CSS files and `className`s to your React components.

### New project tree overview
Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks for updating this one

web/docs/language/features.md Show resolved Hide resolved

When referencing code from `src/client` in your `*.wasp` file, you do it as `@client/relative/path/of/file/in/the/client/dir`.

You can't reference shared code inside the Wasp file, but you can import and use it in all code that lives in `src/client` or `src/server`. Use a relative import to do this. For example, the file `src/server/something.js` can import a shared function from `src/shared/utilities.js` like this:
Copy link
Contributor

Choose a reason for hiding this comment

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

Ok, I see what you meant in the other PR now, thnx.

web/docs/language/features.md Outdated Show resolved Hide resolved
web/docs/language/features.md Outdated Show resolved Hide resolved
entities: [Task]
}
```

And here is how you might use it:
```js {4,18} title=pages/Task.js
```js {4,18} title=client/pages/Task.js
Copy link
Contributor

Choose a reason for hiding this comment

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

I know the previous versions just used pages, but do we want to always preface with src/ moving forward?

web/docs/tutorials/todo-app/auth.md Outdated Show resolved Hide resolved
web/docs/tutorials/todo-app/auth.md Outdated Show resolved Hide resolved
@sodic
Copy link
Contributor Author

sodic commented Nov 9, 2022

Wow @shayneczyzewski, thanks for noticing all of those. I thought I went through it a couple of times, but I guess I was too tired and biased to see it. I'll implement all the changes and mark your comments with 🚀 when they're up.

@sodic
Copy link
Contributor Author

sodic commented Nov 10, 2022

One page I noticed that still references @ext is the main page web/src/pages/index.js, as does one line in features.md (js title="ext/myClientSetupCode.js")

Crap, forgot about the blogs 😅
image

I'll have it ready by tomorrow and let you know. The other stuff you mentioned is fixed and pushed.

@sodic
Copy link
Contributor Author

sodic commented Nov 11, 2022

@shayneczyzewski Ok, all done:

  • Some of your comments have been autoresolved when I committed your suggestions, so don't worry about opening resolved threads (I haven't resolved any of them manually).
  • The ones I resolved and pushed manually are marked with a rocket (:rocket:), but I haven't resolved them
  • I've also updated a few other files we've missed. Blog updates and Changelog edits are covered by PR #809

Copy link
Contributor

@shayneczyzewski shayneczyzewski left a comment

Choose a reason for hiding this comment

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

Awesome job here @sodic. A TON of effort to update all this, so well done 👏🏻 Two minor things but looks ready to roll to me 👍🏻 Great job

web/docs/language/features.md Outdated Show resolved Hide resolved
web/src/pages/index.js Outdated Show resolved Hide resolved
sodic and others added 2 commits November 11, 2022 16:31
Co-authored-by: Shayne Czyzewski <[email protected]>
Co-authored-by: Shayne Czyzewski <[email protected]>
Base automatically changed from filip-js-go-to-definition to main November 11, 2022 16:38
@sodic sodic merged commit 1555662 into main Nov 11, 2022
@sodic sodic deleted the filip-update-docs-new-structure branch November 11, 2022 17:36
@sodic sodic restored the filip-update-docs-new-structure branch November 11, 2022 17:44
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.

2 participants