All Issues
24,993 verified issues
Provide way to use single quotes in jsx
I read this comment saying that "I've never seen anyone write `<div className='a' />`". Well, here's someone 👋 The same way `trailingComma` accepts a string, we could let `singleQuote` do as well. - `'all'` would use single quotes in js as well as jsx - `'js'` (or `true`) would use single quotes in js but not in jsx - `'jsx'` would use single quotes in jsx but not in js
🎣 Using React Hooks in React Native
React Hooks will ship as part of React Native 0.59. If you are interested in using Hooks before then, see my comment below. Original issue: --- - [x] Review the documentation: https://facebook.github.io/react-native - [x] Search for existing issues: https://github.com/facebook/react-native/issues - [x] Use the latest React Native release: https://github.com/facebook/react-native/releases Environment [skip envinfo] OS: Windows 10 Node: 10.11.0 Yarn: Not Found npm: 6.4.1 Watchman: Not Found Xcode: N/A Android Studio: Version 3.2.0.0 AI-181.5540.7.32.5056338 Packages: (wanted => installed) react: 16.7.0-alpha.0 => 16.7.0-alpha.0 react-native: https://github.com/expo/react-native/archive/sdk-30.0.0.tar.gz => 0.55.4 expo: 2.2.0 Description When using React Hooks like `useState` within a function component, I get the following error message. > hooks can only be called inside the body of a function component [code block]
Request to HTTPS with HTTP proxy fails
Summary Trying to do a HTTPS request with a HTTP proxy fails. [code block] Results in: [code block] The problem is already described by @chovy in this ticket, which ended up closed as OP did not have the same problem: https://github.com/mzabriskie/axios/issues/662 @chovy says: > I still have this issue not being able to hit an https url with an http proxy. I can do it fine in request and also in curl from shell. Something not working with axios. I get an EPROTO error. Context - axios version: v0.16.1 - Environment: node v7.10.0, Mac OSX Sierra
promises
now that promises are going mainstream, i'm trying to think of how to make express more async friendly. an idea is to use promises. - `next()` now returns a promise - if middleware returns a promise, that promise is resolved and propagated up `next()`s [code block] Error handlers are now more koa-like: [code block] Pros: - it should be backwards compatible since you don't have to resolve the promise returned from `next()` - much easier error handling including `throw`ing - solves issues shown in https://github.com/visionmedia/express/issues/2255 - no more `fn.length` checking ~_~ - could probably easily upgrade to es7 async functions Cons: - promises - upgrading middleware and supporting both signatures might be a pain in the ass - probably a lot slower
Support New AWS APIGW Binary Responses
This is a Feature Proposal Description Previously, AWS API Gateway did not support binary responses, making it impossible to return images from your serverless API. Now they do (see https://aws.amazon.com/blogs/compute/binary-support-for-api-integrations-with-amazon-api-gateway/). We need to be able to configure HTTP endpoints/events in serverless to use this new functionality.
Support app bundles with 32-bit and 64-bit binaries within them
>Warning > >This release is not compliant with the Play 64-bit requirement. > >The following APKs or App Bundles are available to 64-bit devices, but they have only 32-bit native code: {version code}. > >From August 1, 2019 all releases must be compliant with the Play 64-bit requirement. > >Include 64-bit native code in addition to 32-bit native code in your app. Use the Android App Bundle publishing format to automatically ensure that each device architecture receives just the native code it needs. Learn More This warning appears when trying to publish an `aab` created by `flutter build appbundle` to the Play Store since today. Is this something that I need to worry about or will Flutter automatically resolve this, i.e. is this already planned to be resolved in time?
terraform modules value of count cannot be computed
I was using terraform modules for IAM user creation, add multiple inline policies and multiple policy_arn's to the user after creation. But now I got an issue where I create an IAM_POLICY and get the arn of this policy and i am trying to add it as `policy_arn ="{module.policy.policy_arn}"` but i was getting the error, value of 'count' cannot be computed. My current version of terraform is `0.8.7` module/user/users.tf [code block] module/policy/policy.tf [code block] main.tf [code block] when i do terraform plan i was getting the error the aws_iam_user_policy.user_policy: value of 'count' cannot be computed. now i am not sure. how would i get the arn of the policy created in other module to the current policy_arn to the user. I tried with `terraform 0.9.0 dev` its showing the same issue. but if i first apply with target module on the policy then apply for user, Its not throwing any count error. Its working. I might need a way to tell terraform to apply policy module first then apply user module. It should be done with depends_on but i'm not able to call depends_on on other modules. Could we write a null_resource depending on policy and user module depending on null_resource ? Any suggestions/workarounds or modifications to my modules will be appreciated. thanks.
[0.60.3] App crash on startup when enabling Hermes (enableHermes: true)
App is crashing when I enable Hermes in android/app/build.gradle. App is working fine with react-native 0.60.3 with enableHermes: false Error: ` 07-12 08:06:59.097 20330-20330/com.reactnativememoryprofile E/SoLoader: couldn't find DSO to load: libjscexecutor.so 07-12 08:06:59.123 20330-20345/com.reactnativememoryprofile E/SoLoader: couldn't find DSO to load: libhermes.so 07-12 08:06:59.124 20330-20345/com.reactnativememoryprofile E/AndroidRuntime: FATAL EXCEPTION: create_react_context Process: com.reactnativememoryprofile, PID: 20330 java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:738) at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:591) at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:529) at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:484) at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit>(HermesExecutor.java:20) at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create(HermesExecutorFactory.java:27) at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:949) at java.lang.Thread.run(Thread.java:818) ` React Native version: System: OS: macOS 10.14.5 CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz Memory: 373.31 MB / 16.00 GB Shell: 3.2.57 - /bin/bash Binaries: Node: 10.15.1 - /usr/local/bin/node
Allow for transparent / vibrant window theme
Maybe it can be enabled with `{ transparent: true, vibrancy: 'dark' }` ? https://github.com/electron/electron/pull/7898 — Vibrancy PR https://electron.atom.io/docs/api/frameless-window/#transparent-window
iOS: UI will be blocked when show Alert while closing Modal
When show Alert while closing Modal, the Alert dialog will disappear and the Modal will block the UI entirely even after reload, only on iOS. [code block]
Static Generation / SSG Improvements
Summary Allow Next.js to become fully hybrid by providing methods to do both static generation and server-side rendering on a per-page basis. - Two new per-page data fetching methods - `getStaticProps` - Opt-in to static generation (SSG) at `next build` time. - `getServerSideProps` - Opt-in to server-side rendering (SSR) which renders on-demand. - A new method for statically generating (SSG) a set of routes from dynamic sources - `getStaticPaths` - Return list of parameters for dynamic routes to do static generation (SSG) This RFC exclusively discusses API additions. All new functionality is completely backwards compatible and can be incrementally adopted. This RFC introduces no deprecations. Background When building websites or web applications you generally have to choose between 2 strategies: Static generation (SSG) or server-side rendering (SSR). Next.js instead lets you build hybrid applications that allow you to choose per-page which strategy is used. Starting with Next.js 9, pages without `getInitialProps` get statically optimized and output as `.html` files upon `next build`. However, you might want to do data fetching while generating static pages for your specific use case. For example, to statically generate marketing pages from a CMS or a blog section of the site. Using `getInitialProps` would opt you into SSR in that case. Next.js currently has a `next export` command, that makes the application fully SSG, losing the hybrid nature of Next.js. If
responseType: 'text' return Json Object
[code block] But: [code block] - axios version: v0.16.1
Option to retain multi-line props in JSX/HTML
Right now I'm finding that Prettier collapses JSX attributes onto a single line, up until the column width. This (in my opinion) feels much harder to read as it requires the eyes to constantly scan left to right rather than "glance" at a single block. Would you be open to an option that disables this forced single-line output? Prettier 1.7.4 Playground link%20%3D%3E%20(%5Cn%20%20%3CFoo%5Cn%20%20%20%20hello%3D%7Bbaz%7D%5Cn%20%20%20%20how%3D%7Bare%7D%5Cn%20%20%20%20you%3D%7Ba%7D%5Cn%20%20%20%20hi%3D%7Bc%7D%5Cn%20%20%2F%3E%5Cn)%22%2C%22options%22%3A%7B%22ast%22%3Afalse%2C%22bracketSpacing%22%3Atrue%2C%22doc%22%3Afalse%2C%22jsxBracketSameLine%22%3Afalse%2C%22output2%22%3Afalse%2C%22parser%22%3A%22babylon%22%2C%22printWidth%22%3A80%2C%22semi%22%3Atrue%2C%22singleQuote%22%3Afalse%2C%22tabWidth%22%3A2%2C%22trailingComma%22%3A%22none%22%2C%22useTabs%22%3Afalse%7D%7D) Input: [code block] Output: [code block] Expected behavior: Retain line breaks. Update: I opened this a long while back but after two years of using Prettier I absolutely, without question, and without hestitation, support the settings currently in Prettier and further -- believe that all of these personal preferences simply vanish from sight after using Prettier for more than a few days, as if one never even had them. They vanish into the delight of not having to worry about preferences anymore, and all of the energy / time savings that come from that. I am a 👎 on adding additional configuration in this rega
Add support for AWS Single Sign-On
AWS recently released a SSO service that integrates with Organizations and the AWS Directory Service: https://docs.aws.amazon.com/singlesignon/latest/userguide/what-is.html Currently, the only way to consume this service is via a browser. Shortcuts are provided to copy and paste shell commands to export the appropriate environment variables, but this is unacceptable. Users should not need to use a web browser to authenticate with CLI tools. Other tools such as aws-adfs exist to do this for ADFS, Octa, etc, but there are not currently any for AWS SSO. Since this is a first-party AWS service, aws-cli should support it.
aws-cli-v2 issue with alpine using Docker
I tried to install aws cli v2 with alpine using docker but after installation it doesn't find the aws command even the directories existing. I tried using the following commands [code block]
Feature requests: Typescript definitions
Hi, Since typescript popularity is on the rise and there are no community definitions available for stripe-node I would very much like Typescript definitions. This will help both Typescript users and normal JS users with IDEs that support them like WebStorm and VSCode (even Sublime and Atom have JS hinting plugins that support them). I find using type definitions much easier than going through the documentation. In addition not all the documentation is up to date since I see the functions can optionally return promises if a callback is not passed and it's not documented.
Embedded Android views can't bring up the keyboard
To make sure that Flutter can always bring up the keyboard I made the window of virtual display's presentation non focusable. As a result the embedded Android views cannot bring up the keyboard. We should figure out if there's some window trickery we can do to let the unfocused window bring up the keyboard. Alternatively see if it's possible to dynamically select the focused window when delivering input events.
Docker Compose mounts named volumes as 'root' exclusively
It's about named volumes (so no "data volume container", no "volumes-from") and docker-compose.yml. The goal here is to use docker-compose to manage two services 'appserver' and 'server-postgresql' in two separate containers and use the "volumes:" docker-compose.yml feature to make data from service 'server-postgresql' persistent. The Dockerfile for 'server-postgresql' looks like this: [code block] Adn the docker-compose.yml looks like this: [code block] Then I start everything with `docker-compose up -d`, I enter my server-postgresql container with `docker-compose exec server-postgresql bash`, a quick `ls` does reveal `/volume_data`, I then `cd` into it and try `touch testFile` and got "permission denied. Which is normal because a quick `ls -l` show that `volume_data` is owned by `root:root`. Now what I think is happening is that since I have `USER postgres` in the Dockerfile, when I run `docker-compose exec` I am logged in as user 'postgres' (and the postgresql daemon runs as user 'postgres' as well, so it won't be able to write to `/volume_data`). This is confirmed because when I run this instead: `docker-compose exec --user root server-postgresql bash` and retry to `cd /volume_data` and `touch testFile`, it does work (it's not a permission error between the host and the container, as it is somtimes the case when the container mounts a host folder, this is a typical unix permission error because `/volume_data` is mounted as 'root:root' while user 'postgres' is tryin
How to use Axios with TypeScript when using response interceptors (AxiosResponse issue)
Summary In a project I am migrating to TypeScript (TS), I have a response interceptor `r => r.data`. How do I inform TS that I am not expecting a type of `AxiosResponse`? I've tried overriding using `as Array<...` but that doesn't work as `AxiosResponse` can't be cast as an `Array` (e.g. does not has .length). Thanks! Context - axios version: 0.16.2 - Environment: Visual Studio Code
Vulnerability found
High severity