@@ -603,9 +603,9 @@ Given that you have not yet changed the internal structs, this might feel
603
603
premature, and that's because it is. You don't yet have anything to convert to
604
604
or from. We will revisit this in the "internal" section. If you're doing this
605
605
all in a different order (i.e. you started with the internal structs), then you
606
- should jump to that topic below. In the very rare case that you are making an
607
- incompatible change you might or might not want to do this now, but you will
608
- have to do more later. The files you want are
606
+ should jump to [ that topic below] ( #edit-version-conversions ) . In the very rare
607
+ case that you are making an incompatible change you might or might not want to
608
+ do this now, but you will have to do more later. The files you want are
609
609
` pkg/apis/<group>/<version>/conversion.go ` and
610
610
` pkg/apis/<group>/<version>/conversion_test.go ` .
611
611
@@ -670,7 +670,7 @@ those manually written should be named with a defined convention, i.e. a
670
670
function converting type ` X ` in pkg ` a ` to type ` Y ` in pkg ` b ` , should be named:
671
671
` convert_a_X_To_b_Y ` .
672
672
673
- Also note that you can (and for efficiency reasons should) use auto-generated
673
+ ** Note: ** You should, for efficiency reasons and future updates, use auto-generated
674
674
conversion functions when writing your conversion functions.
675
675
676
676
Adding manually written conversion also requires you to add tests to
0 commit comments