I've taken a couple swings at react native over the past couple years, and every time I do, I run into some recent issue that results in react native not working out-of-the-box when following the getting-started guide. I don't remember which issue it was the past couple times I tried, but this time around I've hit both #14838 and #14767. Are there not regression tests, and if there are, is there no automated check to ensure that they pass before merging to master / cutting a release?
Beyond the obvious confusion / frustration this can cause a newbie, I imagine that it probably leads to a reluctance on the part of existing users of the framework to upgrade. For my part, I'll be hesitant to upgrade RN for fear something will break.
I realize this is pre-1.0 software, but it's been pre-1.0 for more than 2 years, and is widely used. Maybe it's time to put in place a set of regression tests that are automatically enforced prior to merge / release?
I've taken a couple swings at react native over the past couple years, and every time I do, I run into some recent issue that results in react native not working out-of-the-box when following the getting-started guide. I don't remember which issue it was the past couple times I tried, but this time around I've hit both #14838 and #14767. Are there not regression tests, and if there are, is there no automated check to ensure that they pass before merging to master / cutting a release?
Beyond the obvious confusion / frustration this can cause a newbie, I imagine that it probably leads to a reluctance on the part of existing users of the framework to upgrade. For my part, I'll be hesitant to upgrade RN for fear something will break.
I realize this is pre-1.0 software, but it's been pre-1.0 for more than 2 years, and is widely used. Maybe it's time to put in place a set of regression tests that are automatically enforced prior to merge / release?