Gravy | Minecraft protocol/server testing toolkit | Networking library

This is what I meant by iterating over the length of the lists, I have added a code from where you can get an idea of how you can parse.

UPDATED CODE

There are some mistakes in your code, try the following instead:

Add embedded "..."-quoting to the URL, which requires escaping as \"...\":

An intersection type requires food to be both a valid FoodItems object and a valid FoodSide object.

Remember: an intersection type I = A & B means that the set of values of type I is the intersection of the sets of the values of types A and B. Since every value of type I is at the same time a valid A and a valid B, it follows that the properties of the intersection type I must be the union of the properties of the types A and B.

Likewise, a union type U = A | B means that the set of values of type U is the union of the sets of the values of types A and B. Since every value of type U is either a valid A or a valid B, it follows that the properties of the union type U must be the intersection of the properties of the types A and B.

So, what you are saying is that FoodOrder is a type which can be indexed by a number and it returns a FoodItems but at the same time it also returns a FoodSide when it is indexed by a number.

A value of such a type cannot exist, so you actually can't construct anything that would be legal to assign to food.

What would be possible is something like this:

You can do the following:

You can use gsub to create an R function that inserts a "\n" after every n words, where n is an argument.

Is this what you need?

You're absolutely right that you can do what you've described. The downside is that you're forced to expose an API (ie: the fRef prop) for it to work. Not a huge deal if you're a solo developer building an app, but it can be more problematic eg. if you're maintaining an open-source library with a public API.

In that case, consumers of the library won't have access to the internals of a component, meaning you'd have to expose it for them somehow. You could simply do what you're suggesting in your example and add a named prop. In fact, that's what libraries did before React 16.3. Not a huge deal, but you'd have to document it so people know how to use it. Ideally, you'd also want some kind of standard that everyone used so it wasn't confusing (many libraries used the innerRef naming convention), but there'd have to be some consensus around that. So all doable, but perhaps not the ideal solution.

Using forwardRef, passing a ref to a component just works as expected. The ref prop is already standardized in React, so you don't need to go look at docs to figure out how to pass the ref down or how it works. However, the approach you describe is totally fine and if it meets your needs, by all means go with that.

You can try , notice I am adding groupby and head due to your ingre_list have duplicated item within each sub-list, if in real data there is no duplicates , you can remove .groupby(level=0).head(1)