-
Updated
Jul 13, 2020
React Native
React Native is a JavaScript mobile framework developed by Facebook. It allows developers to build Android and iOS mobile apps using JavaScript and reuse code across web and mobile applications.
Here are 19,709 public repositories matching this topic...
react-redux-firebase is the Redux bindings for Firebase. Includes Higher Order Component (HOC) for use with React. It is a very useful library and actively maintained.
- Would I like to make a PR for this?
Yes.
-
Updated
Jul 15, 2020 - JavaScript
Taro能使用wxs吗?
问题描述
最近使用movable-view做了一个拖拽排序的功能,但是由于需要touchmove事件频繁setState来更新movable-view的坐标,导致Android的上的性能体验很差,IOS不会。
看了微信的文档,这种情况可以使用WXS来解决,请问Taro中能否使用WXS?如何使用呢?
参考文档: https://developers.weixin.qq.com/miniprogram/dev/framework/view/interactive-animation.html
https://developers.weixin.qq.com/miniprogram/dev/framework/performance/tips.html
-
Updated
Jul 16, 2020 - Swift
🚀 Feature request
Current Behavior
The type ErrorMessage doesn't have an id property.
Desired Behavior
It'd be nice id?: string would be added to the type ErrorMessage and set on the outermost component that serves as error message.
Suggested Solution
Add id={this.props.id} to the outer component in ErrorMessage.
Who does this impact? Who is this
Issue type:
[x] question
[ ] bug report
[ ] feature request
[x] documentation issue
Database system/driver:
[ ] cordova
[x] mongodb
[ ] mssql
[ ] mysql / mariadb
[ ] oracle
[ ] postgres
[ ] cockroachdb
[ ] sqlite
[ ] sqljs
[ ] react-native
[ ] expo
TypeORM version:
[x] latest
[ ] @next
[ ] 0.x.x (or put your version here)
Description
I tried to create via REST a Bot without setting the username and I get an "Invalid email" error
Steps:
POST http://localhost:8065/api/v4/bots
{"display_name":"Alfred","description":"CMS Automation"}
And response is:
`{"id":"model.user.is_valid.email.app_error","message":"Invalid email","detailed_error":"","request_id":"4by66j8tcjfpmjn65sjjbrwn1y","status_code":4
Related: react-navigation/react-navigation#8160
We have a similar guide for React Router + Netlify https://github.com/expo/examples/tree/master/with-react-router#deploying-to-netlify
We should also have one for Now:
- Create
now.json:
{
"version": 2,
"routes": [{ "handle": "filesystem" }, { "src": "/.*", "dest": "/index.html" }]
}When using a dark theme, the menu bar stays white:
Instead the app should check the current theme and if it's a dark one, the menu bar should be made black (assuming Electron supports this).
I have gone through these following points
- Check latest documentation: https://docs.nativebase.io/
- Check for existing open/closed issues for a possible duplicate before creating a new issue: https://github.com/GeekyAnts/NativeBase/issues
- Use the latest NativeBase release: https://github.com/GeekyAnts/NativeBase/releases
- Check examples from NativeBase KitchenSink ht
-
Updated
Jul 16, 2020 - TypeScript
Users using react: 16.9.0 and react-native: 0.61.5 should not be dragging the fonts folder into the project in xcode. They only need to update the PList.
Description
colorFilters are present in the README.md but are missing an explanation and example in the API.md file
Steps to Reproduce
- Go to the API docs https://github.com/react-native-community/lottie-react-native/blob/master/docs/api.md
Expected behavior: As a Developer I'd like to see how to use colorFilters
Actual behavior: Adequate colorFilter documentation
Custom auth strategy
We are trying to migrate to v4. But now we are failing because we have no clue how to setup a custom auth (api-key) strategy. In v3 we registered our custom api-key strategy at passport like this:
this.passport.use('apikey', new Strategy(verifier));
// and
app.configure(apikey({ header: config.apiKey.header }));Is there any documentation how to setup a custom (api-key) authentic
-
Updated
Jul 16, 2020 - TypeScript
I have issues to get Reactotron working in my jest react-native test environment.
Before running a test I simply do
jest.mock("reactotron-react-native");, but then I receive an error stating
TypeError: Cannot read property 'useReactNative' of undefined
 for more details.
A bit of context, we introduced swr two weeks ago to our codebase. Everything is working fine, but we started to get some reports about some parts of the app being broken in slightly older browsers (Chrome 49, Firefox 59, Edge 18, etc…)
We found out that swr was causing a syntax error in these browsers because webpack by default picked the ESM build (rightly so) but because it's not transp
Issue Description
Icon can accept an object with different attributes
Steps to Reproduce / Code Snippets / Screenshots
Hey there! Ignite CLI seems to be having a problem, eh?
Welllllll, it just might be. First, search the issues to make sure it's not already
here, and if not head over to http://community.infinite.red to
get some help. If you've identified that it's really an Ignite CLI issue, then:
- Explain what's going on and preferably how to replicate the issue (bonus points for a repro app)
- Run
Bug
For the component Marker, the type of value retrieved from onPress={e => console.log(e.nativeEvent)} does not match the documentation NOR the index.d.ts
What is being logged :
{ action: "marker-press", coordinate: { latitude: 0, longitude: 0 }, id: "unknown", target: 77 }
Environment info
React native info output:
-
Updated
Jul 15, 2020 - TypeScript
-
Updated
Jul 14, 2020 - TypeScript
Which OS ?
Windows - Expo - Chrome
Version
Which versions are you using:
- react-native-swiper v1.6.0-rc.3
"expo": "~37.0.3",
"react": "~16.9.0",
"react-native": "https://github.com/expo/react-native/archive/sdk-37.0.1.tar.gz",
Expected behaviour
Swipe right and dot active update
Actual behaviour
Swipe right and dot active not updated, the first dot i
migrate to hooks
avoid deprecated lifecycles
Created by Facebook
Released January 2015
Latest release 2 days ago
- Repository
- facebook/react-native
- Website
- reactnative.com
- Wikipedia
- Wikipedia


Describe the bug
In the config.js
addParametersfunction, if I setisFullscreen: trueand open the webpage, it is fullscreen on startup. But if I setisFullscreen: falseand open the webpage again, it is still full-screen on startup.To Reproduce
isFullscreen: true, open the webpage,isFullscreen: false, open the webpa