-
Notifications
You must be signed in to change notification settings - Fork 196
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
feat(docs): preflight and inflight concepts #3173
Conversation
Hey @Chriscbr, great work! |
@ShaiBer Thanks for the suggestions. I shamelessly stole some text from your tutorial from the intro (I liked it better than my intro) and also reordered some of the ideas of the doc better based on the tutorial. |
Hehe no shame @Chriscbr , I bet in the end I'll steal more from you than you stole from me :) |
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Congrats! 🚀 This was released in Wing 0.23.8. |
First pass at rewriting of the concepts doc page on preflight and inflight. The goal is for this doc to be educational but functional, so I started with trying to motivate the concept as quickly as possible (avoiding marketing / history lessons / manifestos about the future of cloud / pitches about the right way to build applications), though I'd be interested in any feedback / suggestions for improving this intro. (We could also remove the intro entirely, and it might actually be better?) After I tried to come up with a path that goes through the major "mechanics" where the sequence of ideas and code snippets hopefully didn't depend _too_ much on too much knowledge about the standard library resources or about `Json` or optionals etc. I'm also interested in any suggestions for tightening this up / coming up with better examples etc. Since we don't distinguish against capturing reassignable variables or mutable collections as of #3064, I didn't go into much depth about what types of values can be lifted. Also I moved the content about resource identifiers into the "application tree" doc. ## Checklist - [ ] Title matches [Winglang's style guide](https://docs.winglang.io/contributing/pull_requests#how-are-pull-request-titles-formatted) - [ ] Description explains motivation and solution - [ ] Tests added (always) - [ ] Docs updated (only required for features) - [ ] Added `pr/e2e-full` label if this feature requires end-to-end testing *By submitting this pull request, I confirm that my contribution is made under the terms of the [Monada Contribution License](https://docs.winglang.io/terms-and-policies/contribution-license.html)*.
First pass at rewriting of the concepts doc page on preflight and inflight. The goal is for this doc to be educational but functional, so I started with trying to motivate the concept as quickly as possible (avoiding marketing / history lessons / manifestos about the future of cloud / pitches about the right way to build applications), though I'd be interested in any feedback / suggestions for improving this intro. (We could also remove the intro entirely, and it might actually be better?)
After I tried to come up with a path that goes through the major "mechanics" where the sequence of ideas and code snippets hopefully didn't depend too much on too much knowledge about the standard library resources or about
Json
or optionals etc. I'm also interested in any suggestions for tightening this up / coming up with better examples etc. Since we don't distinguish against capturing reassignable variables or mutable collections as of #3064, I didn't go into much depth about what types of values can be lifted.Also I moved the content about resource identifiers into the "application tree" doc.
Checklist
pr/e2e-full
label if this feature requires end-to-end testingBy submitting this pull request, I confirm that my contribution is made under the terms of the Monada Contribution License.