All Issues
24,993 verified issues
Display search results in a tab instead of the side bar
I was talking to a colleague the other day and the only reason he's not using VS Code is because of how the search is implemented in VS Code and I have to agree with his opinion. Both Sublime Text (which I'm used to) and Atom (the editor my colleague is using) feature a search tab. A search tab displays the results much more clearly given that there's much more space available to display them. Instead, VS Code displays them in a "small" side bar. Yes, we can resize back and forth the side bar, but that's a bit annoying. It would be nice to have the search results displayed in a new tab similar to Sublime Text and Atom.
Enforce Trailing Commas by Default
I propose that trailing commas should be enabled by default. IE8 is a non issue for most, and this will provide better diffing. [code block] should be formatted as: [code block] I would also suggest not enabling it for function arguments, considering that this is not in the official spec yet and won't be fully supported without a transpiler like babel. e.g.: [code block] should be formatted as: [code block]
Grid support
Support for `display: grid;` and its props would be swell.
Leave one-line functions alone
Prettier 1.10.2 Playground link [code block] Input: [code block] Output: [code block] Expected behavior: The input was perfectly fine as it stood; it was a nice one-liner, exactly 80 characters long. Breaking it into multiple lines just makes it less clear. Is there a specific reason prettier behaves this way?
App Crash on Android OS 6 Samsung Galaxy S7 SM-G930FD (JSC Crash) 64 bit support A/libc: Fatal signal 11 (SIGSEGV)
Bug Report Crashed on launch Crashed with only this error log traced on android logcat A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 20217. To Reproduce react-native run-android and navigate to second screen from initial route through stack navigator. I am using `React-Navigation 3.6` App crashes as soon as I start going into `react-navigation` and crashing in `Samsung S7 64 bit CPU` device, working fine in other android devices which I am using. Expected Behavior just to work in a stable manner. like in earlier react-native version 0.58 Environment React Native Environment Info: System: OS: Mac OS mojave 10.14 Binaries: npm: 6.4.1 Android Studio: Version 3.2.1 Android 6.0.1 (real device: Samsung S7 SM-G930FD) React Native v0.59.3 Temporary Workaround: When I removed 64 bit ndk filters "arm64-v8a", "x86_64" from ndk abiFilters in defaultConfig block of buidl.gradle by provide only 32 bit support. It works fine. [code block]
NPM audit reports the package with high vulnerability (Denial of Service)
More info https://www.npmjs.com/advisories/1486
Space after function name in declarations
NOTE: This issue is raised due to confusion in #1139. NOTE: Feel free to use the 👍 and 👎 buttons to indicate your preferences, but please refrain from commenting unless you’ve read every comment and made sure yours says something that has _not_ been said before. This issue is _only_ about outputting these spaces: [code block] (Prettier currently does _not_ put spaces in those positions.) > 🗒 NOTE: This issue is _not_ about anonymous functions: > > [code block] > > Anonymous functions are tracked in #3847! The key arguments is: Searchability: You can find any function or method declaration my searching for e.g. `method (` or `identity <`, or even just `name[space]` (mostly). It also provides a clear and immediate difference between _declaration_ and _invocation_. (There are many existing comments in favour of this style, notably: https://github.com/prettier/prettier/issues/1139#issuecomment-316096507 and the majority of the discussion from https://github.com/prettier/prettier/issues/1139#issuecomment-361515396 onwards.)
Add support for cross-repo runners
Describe the enhancement Having an agent _per_ repo is very tedious and frustrating. It would be nice to have agents that can work across repositories to prevent potentially having hundreds of agents to maintain (with rotating tokens) across hundreds of repos Code Snippet n/a Additional information n/a
Need to restart or flutter clean too often
--- --- --- The following note was added by @tvolkert on Oct 16, 2018 If you are affected by this bug, please fill out the following form! https://goo.gl/forms/eFPT6A3jAD8clU4o2 (Survey to gather information about this bug) --- --- --- Steps to Reproduce When I (or one of my teammates) run flutter `flutter run` (or with the run/debug button on IntelliJ and VSCode) on an AVD or on real devices, the installed version is always behind the newest one and I always need to restart the app or even sometimes `flutter clean`. This is a problem especially when the build on the AVD/real device crashes, and the only solution here is to `flutter clean`, even when I stop the app running and do `flutter run` again. The same happens when building and installing production APKs: When I run `flutter build` and `flutter install`, the installed APK isn't updated. If I run flutter clean, and next, again, `flutter build` and `flutter install`, the installed APK is up-to-date. Flutter Doctor: [code block]
Project dead?
Is the project dead? Are new maintainers sought? - 97 open pull requests - 411 open issues
Allow for existing containers (allow sharing containers across services)
I think it would be useful if compose could allow you to specify containers that may already exist, eg: [code block] If the container 'shareddata' did not exist, it would be created as usual. If, however, that container already existed, the allow_existing: true setting would not complain about a duplicate container, instead just skipping creation (and perhaps it would try to bring the container up if it were stopped?). I haven't python-ed in a long time, but I might be able to create a PR for this feature if someone wanted to give me a little guidance on where the best place to start looking into the code would be.
Use with React Router 4
Is it possible to use next.js with the new react router v4?
[Next 9] out of memory when building the app
Bug report Describe the bug Moving an application from Next 8 to Next 9. When I run `next build` the process goes out of memory and it cannot build the application. FYI, it's an application with 20 routes more or less. To Reproduce That's hard to reproduce as I don't have any idea what went wrong. Next 8 compiles without issue but not Next9. Here's the stack trace. If you know how to get a more descriptive output, let me know and I will provide: [code block] Expected behavior It should build Screenshots If applicable, add screenshots to help explain your problem. System information - OS: macOS - Node: 10.13.0 (it will have to work with node 8.X too) - Version of Next.js: 9.0.1 Additional context Add any other context about the problem here.
Image cannot show image in iOS 14
Image cannot show image in iOS 14, but can show location, like: <Image source={ require('./images/add_scan_images.png') } /> Environment: Xcode Version 12.0 beta (12A6159) Simulator: IPhone SE - 2nd generation - 14.0 "react": "16.11.0", "react-native": "0.62.2"
Don't send default header
If a header has been set as a default, there does not appear to be any way to skip it on an individual request. Setting `null` or `undefined` doesn't do anything.
Suggestion: option to include undefined in index signatures
Update: fixed by `--noUncheckedIndexedAccess` in TypeScript 4.1 --- Update: for my latest proposal see comment https://github.com/Microsoft/TypeScript/issues/13778#issuecomment-406316164 With `strictNullChecks` enabled, TypeScript does not include `undefined` in index signatures (e.g. on an object or array). This is a well known caveat and discussed in several issues, namely https://github.com/Microsoft/TypeScript/issues/9235, https://github.com/Microsoft/TypeScript/issues/13161, https://github.com/Microsoft/TypeScript/issues/12287, and https://github.com/Microsoft/TypeScript/pull/7140#issuecomment-192606629. Example: [code block] However, it appears from reading the above issues that many TypeScript users wish this wasn't the case. Granted, if index signatures did include `undefined`, code will likely require much more guarding, but—for some—this is an acceptable trade off for increased type safety. Example of index signatures including `undefined`: [code block] I would like to know whether this behaviour could be considered as an extra compiler option on top of `strictNullChecks`. This way, we are able to satisfy all groups of users: those who want strict null checks with or without undefined in their index signatures.
Provide a way to add the '.js' file extension to the end of module specifiers
In order to use es6 modules in the browser, you need a .js file extension. However output doesn't add it. In ts: `import { ModalBackground } from './ModalBackground';` In ES2015 output: `import { ModalBackground } from './ModalBackground';` Ideally I would like this to be output `import { ModalBackground } from './ModalBackground.js';` That way I can use the output in Chrome 51 [code block] Related to https://github.com/Microsoft/TypeScript/issues/13422
Firestore import - Bundle size is huge
import firebase from '@firebase/app'; import '@firebase/firestore'; // this one is very very huge. I am using only firestore in my app. How to reduce the bundle size of firestore?
Missing request token for request: <NSURLRequest: 0x60000253e5a0> { URL: file://
Description I just upgraded to RN 0.63.0 and all fine, but only for upload using axios, i get [code block] React Native version: System: OS: macOS 10.15.5 CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz Memory: 163.19 MB / 8.00 GB Shell: 5.7.1 - /bin/zsh Binaries: Node: 12.16.1 - /usr/local/bin/node Yarn: 1.22.4 - /usr/local/bin/yarn npm: 6.13.4 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman Managers: CocoaPods: 1.9.1 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: iOS 13.4, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2 Android SDK: API Levels: 22, 23, 25, 26, 27, 28, 29 Build Tools: 23.0.3, 27.0.3, 28.0.3, 29.0.0, 29.0.2 System Images: android-28 | Google Play Intel x86 Atom, android-29 | Google Play Intel x86 Atom, android-R | Google APIs Intel x86 Atom Android NDK: Not Found IDEs: Android Studio: 4.0 AI-193.6911.18.40.6514223 Xcode: 11.4.1/11E503a - /usr/bin/xcodebuild Languages: Java: 1.8.0_221 - /usr/bin/javac Python: 2.7.16 - /usr/bin/python npmPackages: @react-native-community/cli: Not Found react: 16.13.1 => 16.13.1 react-native: 0.63.0 => 0.63.0 npmGlobalPackages: react-native: Not Found Steps To Reproduce Here is my code snippet and that gives me error [code block] Expected Results Should upload file, it was fine in 0.62.2
Feature Request: breakBeforeElse
I know the goal of prettier is to standardize on a style, but it is also difficult since this did not come out at the same time as the language. Our team uses the exact same style as prettier except placement for `else` statements. It is effectively blocking us from adopting this awesome library. We prefer break before `else` to allow for cleaner comments. [code block] Which is nicer than. [code block] However this is preference and would be awesome if this was added as an option to prettier. @vjeux showed how easy it is to do https://github.com/prettier/prettier/pull/837 and apparently @jlongster likes it :) https://twitter.com/jlongster/status/834407714965057540