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

Migration Guide: 0.4 to 0.5 #107

Merged
merged 19 commits into from
Apr 6, 2021
Merged

Conversation

cart
Copy link
Member

@cart cart commented Mar 9, 2021

This adds the initial migration guide page. This is intended to be a collaborative effort. To contribute, leave a comment on 0.4 to 0.5 migration guide issue claiming one or more unclaimed items, then create a pull request to this branch.

Each migration item should have a description of the change (with rationale if you anticipate a negative response), descriptions of breakage symptoms (when that is relevant and non-obvious), and small before/after code snippets where relevant.

Todos:

  • fill in remaining migration items
  • add a link to the 0.5 release blog post (when it drops)
  • try improving the code block formatting in headers (the scale is a bit off)

}

// 0.5
fn foo(r1_thru_3: (Res<Thing1>, Res<Thing2>, Res<Thing3>), r4: Res<Thing4>, ... r15: Res<Thing15>) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
fn foo(r1_thru_3: (Res<Thing1>, Res<Thing2>, Res<Thing3>), r4: Res<Thing4>, ... r15: Res<Thing15>) {
fn foo(r1_thru_3: (Res<Thing1>, Res<Thing2>, Res<Thing3>), r4: Res<Thing4>, ... r12: Res<Thing12>) {

Copy link
Contributor

Choose a reason for hiding this comment

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

oh, I was too quick to comment. I see now how its using the nested for the first three ^^

Copy link

Choose a reason for hiding this comment

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

Maybe it would be good to pattern match the first argument to help with noticing the change?

Suggested change
fn foo(r1_thru_3: (Res<Thing1>, Res<Thing2>, Res<Thing3>), r4: Res<Thing4>, ... r15: Res<Thing15>) {
fn foo((r1, r2, r3): (Res<Thing1>, Res<Thing2>, Res<Thing3>), r4: Res<Thing4>, ... r15: Res<Thing15>) {

@NiklasEi
Copy link
Member

NiklasEi commented Mar 12, 2021

How could I contribute to this? Am I supposed to make PRs against the branch of carts fork?
In bevyengine/bevy#1601 it sounds like the migration guide could be collaborative work.

@alice-i-cecile
Copy link
Member

How could I contribute to this? Am I supposed to make PRs against the branch of carts fork?

@NiklasEi This is correct :) Ideally note which issues you're tackling in #1601 so then we don't get duplicated work first.

@cart cart merged commit 0f3d76f into bevyengine:master Apr 6, 2021
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.

8 participants