I've been looking at this and it seems that this is a pagination issue.
The REST API seems to only be returning 100 elements, even though there are more.
Looking at the Pagination classes in the corresponding module of the BlueOcean repo, I see that 100 is indeed the default value for pagination in the API.
I first tried to figure out how to obtain the next page for steps, but it seems to me that the "/steps" API operation is missing the pagination implementation, so it is only returning the 100 first elements, as a default config.
So this probably needs an API enhancement for that operation to include GET parameters to allow pagination. And then probably a change to the Front-end to add some sort of dynamic loader for steps when you scroll further than the first 100 elements, for instance. That would includes a few changes in the corresponding React components as well, to achieve that behavior
I've been looking at this and it seems that this is a pagination issue.
The REST API seems to only be returning 100 elements, even though there are more.
Looking at the Pagination classes in the corresponding module of the BlueOcean repo, I see that 100 is indeed the default value for pagination in the API.
I first tried to figure out how to obtain the next page for steps, but it seems to me that the "/steps" API operation is missing the pagination implementation, so it is only returning the 100 first elements, as a default config.
So this probably needs an API enhancement for that operation to include GET parameters to allow pagination. And then probably a change to the Front-end to add some sort of dynamic loader for steps when you scroll further than the first 100 elements, for instance. That would includes a few changes in the corresponding React components as well, to achieve that behavior