:tada: More Information about Crafting items

[rw-root]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Feel free to reference another issue number if yours is distinct but related.

• if we, for example, look at the Data for the Warframe "Ash" we can see that under components the "Chassis" do not show the components you need to craft the Chassis itself, it only shows where you can find the blueprint.

Describe the solution you'd like
A clear and concise description of what you want to happen.

• I would like there to be another field of components that are required for crafting said item.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

• i have considered that the recipes that are that deep in the tree could be added to the base list of items and the recipes itself reference to said item

Additional context
Add any other context or screenshots about the feature request here.

• there is no additional context i can think of right now.

thank you for your time.

[TobiTenno]

up to this point we haven't done nested components because it complicates other existing issues (like if you're familiar with how images sometimes exist and sometimes don't, because of how they're stored as shortened versions of the name, and conditionally have parts removed.

additionally, it tends to rather bloat data, and we already have a rather large package to load into memory for servicing over the api, for example

[TobiTenno]

if @AyAyEm at this point wants to do his name shortening and attempt to build a list of dupes to decrease the dupes, i'm willing to try that for the images part.

i'm worried that this request, though, will keep coming up, and i'm not sure the right long-term approach, because we're going to eventually have requests for deeper and deeper resolutions if we have any that have second and third level nesting, is my main concern.... it slows down the whole process, which is already pretty slow

[AyAyEm]

For deep nested components we would probably need to refactor how we handle them, a sql like approach would be best, just add the component unique name and amount, that way if the component has components it'll always be 1 level deep and with very little duplicated data (just the uniqueName in this case).

I don't know how the images is relevant to this issue. Also i'll not be able to help with the code.

[SlayerOrnstein]

Iirc the public export has a recipe export, you could just extract it as a dependency like the image manifest. That way you'd have an easier way of "connecting" them.