0.11 Migration: `FreeSystemSet` doesn't exist anymore and isn't mentioned in the migration guide

Open nicopap opened this issue 2 years ago • 4 comments

Just trying to deal with 3rd party code that uses FreeSystemSet. I suppose the correct migration instructions would be to just accept a SystemSet instead.

Jul 30 '23 14:07 nicopap

Also true of the other BaseSet features such as no_default_base_set

Jul 30 '23 14:07 nicopap

oh i JUST ran into this myself, good timing.

Jul 30 '23 15:07 laundmo

Yeah I was trying to port bevy_spatial. Since now you have to add systems to specific schedule, you also need to accept a schedule parameter to your AutoT::build method.

Jul 30 '23 15:07 nicopap

oh funny i was doing the same (porting bevy_spatial) good news is i'm almost done except examples (its on a branch now)

Jul 30 '23 19:07 laundmo