Freedzio

I've wrapped the `Tabs` component in `` and tab content became visible. However, in my case content is dynamic, meaning it's not always the same height (tab height doesn't change...

Here's what I've come up with ``` {createTabs()} ``` The whole view is wrapped in ScrollView, so setting minHeight seems to solve the problem. However, this solution isn't perfect, becasuse...

Hmmm Maybe put subclass giving features in `feature_choices` prop in data from `classes/${class)/levels/${level}` endpoint? This way, IMO there is even more consistency Example: data from `level` endpoint ``` ... "feature_choices":...

When you put it that way, ye, my propositon would stir some disinformation. `feature_specific` approach is cleaner. It indicates that this feature has some logic/complexity behind it and allows the...

As I work on my app, I am having more and more ideas. Given there will be `feature_specific` prop, how about putting there data about bonuses? For example, in `Fighitng...

hmm, so `proficiency` property on `feature` object? This way, the data comes from feature, bot the subclass. Also, I agree on the idea of expanding the features. For example, it...

You seem to be missing my point `typeconv` sees `Date` type as a user defined type and treats it as such. But it is not user defined. One would not...

what frontend are you using?