Граф коммитов

3 Коммитов

Автор SHA1 Сообщение Дата
Nick Gerleman e5e33e51f2
npm postinstall and preinstall scripts pose a potential attack vector. We previously disabled their use in our repo, but I enabled them so we could use patch-package, to alter Picker for consumption in our repo. All changes have landed upstream, so we shouldn't need to do this anymore. (#9061)
Remove the picker patches, patch-package usage, and disable running bin scripts.
2021-11-05 08:42:58 +00:00
Nick Gerleman bf9a13dfd1
Remove or Migrate Usages of Picker (#8432)
* Remove or Migrate Usages of Picker

The [6/23 RN integration](https://github.com/microsoft/react-native-windows/pull/8357) removes Picker. We still have a few usages of it in custom RNTester examples or the like. This change removes all usages of it from our own code, either removing where inapplicable, or using the reccomended community module instead. This gives us a bit of real coverage of a module in our repo, but we only require it for the RNW RNTester fork instead of including it in RNW itself.

This exposed an issue where we broke usageof RNW with existing community modules (see https://github.com/microsoft/react-native-windows/issues/8430). We workaround this with patch-package for now, which also has us enabling yarn scripts again so we can hook postinstall.

Playground and playground-win32 are both updated to support autolinking, and it is tested that community module picker controls work correctly in them.

* yarn format

* Try adding WinUI 3 Support to @react-native-picker/picker
2021-08-17 17:11:06 -07:00
dannyvv 4e343f25d8
Disable running post install scripts for yarn packages (#7068) 2021-02-08 12:27:54 -08:00