It seems that step images have to have filenames as specified in the cooklang docs—i.e., dish.1.jpg, dish.2.jpg. These images will show up in the CLI server under steps 1 and 2, regardless of what section these steps figure in. In other words, it seems the step count iterates continuously regardless of section dividers.
In the iOS app, however, this does not seem to work. If you have a two-step, two-section recipe, where step 1 is in section 1 and step 2 is in section 2, the image "dish.2.jpg", will not appear anywhere (dish.1.jpg, will appear in step 1 section 1). After some trial and error, it seems for the iOS app you have to specify two levels of steps for the images to show up: the section number and the step number relative to the section number. The second image will appear under step 2 (section 2), with the filename "dish.2.1.jpg."
If you adopt the iOS naming convention, however, the images no longer show up in the CLI server. Could either CLI adopt iOS convention, or vice versa? Or even better: could both adopt a more robust image step filename parser and figure out the logic the user is using. I can illustrate the problem with more detail if necessary.
It seems that step images have to have filenames as specified in the cooklang docs—i.e., dish.1.jpg, dish.2.jpg. These images will show up in the CLI server under steps 1 and 2, regardless of what section these steps figure in. In other words, it seems the step count iterates continuously regardless of section dividers.
In the iOS app, however, this does not seem to work. If you have a two-step, two-section recipe, where step 1 is in section 1 and step 2 is in section 2, the image "dish.2.jpg", will not appear anywhere (dish.1.jpg, will appear in step 1 section 1). After some trial and error, it seems for the iOS app you have to specify two levels of steps for the images to show up: the section number and the step number relative to the section number. The second image will appear under step 2 (section 2), with the filename "dish.2.1.jpg."
If you adopt the iOS naming convention, however, the images no longer show up in the CLI server. Could either CLI adopt iOS convention, or vice versa? Or even better: could both adopt a more robust image step filename parser and figure out the logic the user is using. I can illustrate the problem with more detail if necessary.