Here's what's popular on GitHub today...
GraphQL
-
Updated
Dec 20, 2020 - Objective-C
-
Updated
Dec 22, 2020 - C++
-
Updated
Dec 21, 2020 - Jupyter Notebook
Pixel Art Tools
Creating pixel art for fun or animated sprites for a game? The digital artist in you will love these apps and tools!
Codecov | Code Coverage Reports
Codecov provides highly integrated tools to group, merge, archive and compare coverage reports.
- Uploads coverage reports from your CI
- Merges all builds and languages into one beautiful, coherent report.
- Displays data in GitHub via our Sourcegraph browser extension.
Is your team using GitHub Enterprise? If so, check out Codecov Enterprise.
Do you have less than 5 users in your organization? You can sign up for free on codecov.io.
-
Updated
Dec 22, 2020 - Python
-
Updated
Dec 21, 2020 - C++
-
Updated
Dec 22, 2020 - C#
-
Updated
Dec 23, 2020 - C#
-
Updated
Dec 22, 2020 - JavaScript
-
Updated
Dec 22, 2020 - Dart
-
Updated
Dec 23, 2020 - TypeScript
-
Updated
Dec 22, 2020 - Shell
-
Updated
Dec 21, 2020 - Go
🚀 Feature Proposal
From #10123.
When we find a config file, we should also check if there is a jest entry in any sibling package.json and print a warning that it is ignored.
If using --config we should not warn.
Motivation
Helps the user have correct and consistent
-
Updated
Oct 1, 2020 - Jupyter Notebook
图片分辨率问题
1、能否设置图片分辨率尺寸。
2、添加图片或替换图片时,是否可以固定长宽比自动缩放。
单选或者多选增加横放排列方式
Describe the bug
Storybook --host attribute it changes localhost where it should change network host.
start-storybook -h 192.168.89.89 -p 9009
Local: http://192.168.89.89:9009
On your network: http://10.0.2.15:9009
The expected result should be like the one bellow
Local: http://localhost::9009/
On your network: http://192.168.89.89:9009
During development with Firebase, I came through an error and the URL in that error is broken.
Specifically, the links in firebase_core_exceptions.dart
E.g.
-
Updated
Dec 22, 2020 - C++
LogRocket
LogRocket lets you replay problems as if they happened in your own browser. Instead of guessing why errors happen, or asking users for screenshots and log dumps, you can replay sessions to quickly understand what went wrong.
LogRocket records pixel-perfect videos of user activity along with console logs, JavaScript errors, network requests, and browser metadata. It also has deep integrations with React, Redux, Angular and Vue.js to record application state.
Whenever the server isn't running and you have a cached version (didn't close the tab) of the admin log page, the log entries go blank with no information about what happened.
Maybe we need to show a "failed to connect" or leave the old log entries around?🤔