Giter VIP home page Giter VIP logo

coderplanets / coderplanets_web Goto Github PK

View Code? Open in Web Editor NEW
337.0 337.0 39.0 716.63 MB

maybe the most sexiest community for developers based in china, build with React, Mobx/MST, GraphQL, Styled-Components, Rxjs, Ramda ... and ❤️

Home Page: https://coderplanets.com

License: GNU General Public License v3.0

JavaScript 9.50% Dockerfile 0.03% Shell 0.07% Makefile 0.40% Handlebars 0.19% TypeScript 89.82%
jest mobx nextjs ramdajs react rxjs styled-components

coderplanets_web's People

Contributors

dependabot-preview[bot] avatar dependabot[bot] avatar greenkeeper[bot] avatar kyloc20 avatar mydearxym avatar xiejiss avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

coderplanets_web's Issues

4201 错误

在 Python 节点,选择“闲聊”话题,发布帖子,编辑,预览,发布,报错:

image

better design for article viewer

据不少用户反映, 在宽屏显示器下文章的浏览组件从右侧滑出会增加颈椎病风险,看起来很不舒服。现在初步考虑以下折中办法:

  1. 笔记本 15 寸以下保持默认风格不变。
  2. 中等大小尺寸的屏幕参考 https://feedly.com 的响应式设计
  3. 宽屏则以 模态框的形式屏幕正**弹出

期待各位朋友的意见反馈.

An in-range update of react-resize-detector is breaking the build 🚨

The dependency react-resize-detector was updated from 3.1.2 to 3.1.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

react-resize-detector is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 2 commits.

  • 3c4dfe9 3.1.3
  • 7159cd7 Replace lodash.isarray in favor of Array.isArray. Closes #46

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of draft-js-mention-plugin is breaking the build 🚨

The dependency draft-js-mention-plugin was updated from 3.1.2 to 3.1.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

draft-js-mention-plugin is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

move store to it's own container

currently all stores is placed in stores dir:

stores/
├── AccountEditorStore
│   ├── index.js
│   └── test
│       └── index.test.js
├── AccountStore
│   ├── index.js
│   └── test
│       └── index.test.js
├── AccountViewerStore
│   ├── index.js
│   └── test
│       └── index.test.js
.......

i am think move each store to it's own container, so the container dir looks like:

containers/Banner/
├── ActivitiesRootBanner.js
├── CheatsheetRootBanner.js
├── CommunityBanner.js
├── index.js
├── lang.js
├── logic.js
├── schema.js
├── store.js
├── styles
│   ├── activities_root_banner.js
│   ├── cheatsheet_root_banner.js
│   ├── community_banner.js
│   └── index.js
└── tests
    └── index.test.js
    └── store.test.js

the top stores dir will only contains rootStore, storeIndex and store creator

Pros and Cons

  1. container's all functionality now locate in one place
  2. switch file inside container style/logic/store ... now make sense

Cons

need refactor the code and boilerplate generator, that's a lot of work..

details

  1. rename storeIndex -> index.js
  2. rename index.js -> init.js
  3. rename all xxx-store in logic -> store

An in-range update of @commitlint/cli is breaking the build 🚨

The devDependency @commitlint/cli was updated from 7.1.2 to 7.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@commitlint/cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

takeUtil not work in network TIMEOUT workflow

when this.stop$ been called, the takeUtil operator not cancel the ajax request as expected.

see details in source file

    this.mutate$ = this.mutateInput$.pipe(
      debounce(() => timer(300)),
      switchMap(q =>
        mutatePromise(q).pipe(
          timeoutWith(TIMEOUT_THRESHOLD, TimoutObservable),
          takeUntil(this.stop$)
        )
      )
    )

city create request & suggestion

If you do not find your city in the same city section, you are welcome to apply in the comments section below. Any suggestions and feedback about the City section are also welcome in the comments section.

I look forward to your valuable comments.

translate:

如果你在同城版块没有找到你所在的城市,欢迎在下方评论区申请创建。有关同城版块的任何建议与反馈也欢迎在评论区讨论。

期待各位热心朋友的意见。

An in-range update of babel-plugin-styled-components is breaking the build 🚨

Version 1.7.0 of babel-plugin-styled-components was just published.

Branch Build failing 🚨
Dependency babel-plugin-styled-components
Current Version 1.6.4
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

babel-plugin-styled-components is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes v1.7.0

This minor release reintroduces "pure" annotation of styled components and the various library helper methods. It is off by default, so if you want to turn it on pass this config to the plugin:

.babelrc

{
  "plugins": [
    ["babel-plugin-styled-components", { "pure": true }]
  ]
}

"pure" annotation helps signal to minifiers like uglify that a piece of code is safe to remove if not used in at least one other place. This means if you have any components lying around that you're not actively using, they'll be dead code eliminated with this featured enabled. That goes for the helpers too like createGlobalStyle, keyframes, and css.

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.

move init logic to constructor

  1. children componentDidMount fired BEFORE parent componentDidMount
  2. children componentWillMount fired AFTER parent componentWillMount
  3. componentWillMount will be deprecated in future

in complex containers like Typewriter, the order will cause chaos || bugs

see discuss in facebook/react#5737

An in-range update of apollo-link-error is breaking the build 🚨

The dependency apollo-link-error was updated from 1.1.0 to 1.1.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

apollo-link-error is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

如何在一開始就決定語系?

您好, 這個框架使用的是 react-intl 的多語系套件
請問如何在一開始進入時, 就設定語系呢?

現在看預設都是中文, 必須進入後才切換語系

使用中文的朋友请进来 :)

非常感谢你对 coderplanets 的关注!

在你发现 coderplanets 的任何问题并决定提交 issue 前,请务必遵守开源社区惯例,使用英文提交,以方便不同文化背景的开发者之间的相互交流,

相应的,我的回复也尽量会使用英文,这无关英文水平的好坏和意识形态的差异, 只是出于对世界各地开源贡献者之间的惯例的尊重。如果你实在不知道用英文怎么写,可以先用母语描述出问题,然后借助一些随手可得的工具转换成英文即可,谢谢合作。

但同时,虽然现阶段网站的用户大多数在大陆,但在 coderplanets 上创作的内容、分享等等并不局限于简体中文,世界很大,我们同时欢迎各种语种来源的信息。这也是 coderplanets 在一开始就没有采用国内流行的自带局域网特效的 xxx china / xxx 的拼音等作为域名的原因之一。

感谢你的理解和支持, 祝好。

An in-range update of graphql-tag is breaking the build 🚨

The dependency graphql-tag was updated from 2.9.2 to 2.10.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

graphql-tag is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 6 commits.

  • 449834f 2.10.0
  • 27fdc8a Adding support for graphql@14 (#211)
  • c5a32a6 Revert "Add DocumentNode to gql declaration (#196)" (#218)
  • ae792b6 Add DocumentNode to gql declaration (#196)
  • 1648b6d Update deprecated package name (#186)
  • 1fd2c9d Update copyright year (#184)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

global ErrorBox design

ErrorBox handles global NETWORK / TIMEOUT / GRAPHQL error

GRAPHQL has further 3 types of errors:

  • changeset error: message -> array[object]
    image
  • custom error message -> string
    image
  • GraphQL schema parse error -> array[string]
    image

An in-range update of react-tooltip is breaking the build 🚨

Version 3.8.2 of react-tooltip was just published.

Branch Build failing 🚨
Dependency react-tooltip
Current Version 3.8.1
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

react-tooltip is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes v3.8.2

3.8.2 (2018-09-11)

Bug Fixes

  • index.js: Use correct orientation when mouse enters (4a0da8b), closes #388
Commits

The new version differs by 4 commits.

  • be89b82 Merge pull request #413 from an4ger/master
  • 6add4b6 Merge remote-tracking branch 'upstream/master'
  • ab9c109 fix travis issues
  • 4a0da8b fix(index.js): Use correct orientation when mouse enters

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

react-hot-loader warning in console

warning in the console

'React Hot Loader: this component is not accepted by Hot Loader. \n' + 'Please check is it extracted as a top level class, a function or a variable. \n' + 'Click below to reveal the source location: '

need new site text-logo

current site text-logo looks chaos in different browsers, mainly because the font-family: cursive is not working in all browsers?

chrome on mac
image

my firefox on mac
image

someone's firefox on mac
image

someone's firefox on window
image

so, a new look-same-in-all-place logo is needed, and because the logo should adopt for all themes(light, dark, ...), the logo must create in SVG format so i can change color by code.

the group / org / team (团队/机构) entry

关于团队(或者叫机构、公司等)主入口的设计草图

目前计划在网站主要功能稳定一段时间后开发并推出

image

一些想法

  1. 暂时命名为 "团队", 个人觉得这个名字比机构、公司什么的更纯粹一些
  2. 团队几乎和现有的社区在实现层面上保持一致,也分帖子、招聘、订阅等等版块,按需开通即可。
  3. 开通团队需要基本的团队信息认证,且仅限高级用户,以保证高质量。
  4. 如果用户订阅某团队,Sidebar 的订阅列表需出现 “团队”的 tab 选项,以便于和订阅的 "社区", "专栏" 等区分开来。
  5. 团队的主要成员即等同于社区的编辑概念, 在 UI 上需作出一定的区分。
  6. 团队和 "专栏" 的差异主要是团队面向一群人,而专栏一般面向个人。
  7. 其他。。

关于团队的想法,期待各位朋友的宝贵意见。

add User Heat Map thread

see example : g2 map

image

details

the world-geo json is too big (95kb gzip), we should tools like custom geo map data to build a custom one (currently the format seems not right), bottom line --- reduce it by manually ...

as for china-cities, see the example

in production, should use pwa to store the json in browser-side, just load city-user-count from server side

args

  var chart = new G2.Chart({
          id: 'c1',
          width: 750,
          height: 500,
          plotCfg: {
            margin: [10, 105],
            border:{
              fill:'rgba(68, 79, 93, 0.9)'
            }
          }
        });
        chart.legend(false);
        chart.coord('map', {
          projection: 'albers',
          // 指定投影方法的基本参数,[λ0, φ0, φ1, φ2] 分别表示**经度、坐标起始纬度、第一标准纬度、第二标准纬度
          basic: [112, 0, 25, 46], 
          max: [16.573, -13.613], // 指定投影后最大的坐标点
          min: [-27.187, -49.739] // 指定投影后最小的坐标点
        });

g2 API

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

better ErrorBox design

image

The current ErrorBox is presented in the form of Modal. In order to facilitate the developer to debug in advance, the content displayed is relatively raw.

If you have better ideas or suggestions, please leave comments below.

translate

当前 ErrorBox 以 Modal 的形式呈现,为方便开发者前期调试,展现的内容比较原始。
如果你有更好的想法或建议,欢迎在评论区提出。

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.

Apollo client cannot parse server 400 status code as GraphQL-Parse-Error

giving a GraphQL-schema like this:

const createCommunity = gql`
  mutation(
    $title: String!
    $desc: String!
  ) {
    createCommunity(
      title: $title
      desc: $desc
    ) {
      id
    }
  }
`

if you query with required field missing :

{
  title: "title"
}

Apollo-client will not treat this as GraphQL parse error but a Network Error, because Apollo client treat web status > 300 as a Network error.

to work around this, we should currently change our query to:

{
  title: "title"
  desc: "",
}

this will raise GraphQL-Parse-Error as we expect.

related issue

client side GraphQL query cache

Apollo Client has the ability to cache query in client side:

export const client = new ApolloClient({
  link,
  /* cache: new InMemoryCache(), */
  cache: new InMemoryCache(),
  connectToDevTools: true,
  /* shouldBatch: false, */
  // defaultOptions,
})

the tricky part is to refresh cache when user do some mutate operation, like create post (post list should then be update)。

the official writeQuery solution mentioned in apollo doc is complex and adjectived.

need better solution.

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Architecture feels very good

Architecture feels very good, but no documentation Do not know how to use the characteristics of this framework,
Are you considering adding files?

should have columns / zhuanlan

url

columns should focus on columns-name not author-name
cps/columns/xxx
or
cps/zhuanlan/xxx

details

  1. user can add other users articles to his/her own columns
  2. columns has many authors, and manager too
  3. articles has field says: this article is collected by follow columns: ...
  4. articles in columns has an original label

is it necessary to add 3rd-party login(第三方登录)?

各位好,目前 coderplanets 仅支持 github 作为第三方登录选项, 最初这么设计的原因是--我主观的认为作为一个面向开发者的论坛,github 提供的授权功能就已经够用(同时足够简单和纯粹), 但随着开发工作的推进,我发现仅提供 github 作为唯一的登录方式已经渐渐跟不上一些常见的需求,比如(但不限于):

  • 在某些地区/时段,github 的鉴权请求可能会被社会主义特色价值观阻挡..
  • 想发布招聘信息但没有 github 账号,比如人事/猎头朋友..
  • 与水平无关,不少开发者并没有 github 账号 ..
  • 设计师朋友,确实很少有 github 账号的 ..
  • 一些我暂时没想到但又客观存在的场景 ..

所以我初步计划增加以下社交账号作为补充:

image

期待各位热心朋友的意见:

  • 你是否觉得有必要增加其他的第三方登录选项 ?
  • 如果有必要,上图中的第三方登录选项是否可以满足你的需求?

有些国内的社交账号集成起来手续相对繁琐一些,可能需要一些时间。

谢谢各位。

same city company (同城公司) design

image

About the design of the same city company

At present, there is only one tab in the same city. I plan to add a company Tab. Some ideas are as follows:

  1. The company is displayed as a card and is still presented as a post after clicking.
  2. The display content includes company introduction, main business and so on.
  3. There can be recruitment information, but only in the form of a recruitment link, because there is a dedicated recruitment section.
  4. Brain Hole: You can have a company's anonymous rating/comment/spit system, similar to FB's secret page.
  5. Brain Hole: There can be an anonymous salary, similar to GlassDoor.
  6. Some other interesting things.

Regarding the design of the same city company, I look forward to your valuable comments.

translate:

关于同城公司的设计

目前同城只有帖子一个Tab, 计划添加一栏公司(Company) 的Tab,一些想法如下:

  1. 公司以卡片形式展示,点击后仍然以帖子的方式呈现。
  2. 展示内容包括公司介绍,主要业务等。
  3. 可以有招聘信息,但是只能以招聘链接的形式,因为有专门的招聘版块。
  4. 脑洞:可以有公司的匿名评分/点评/吐槽系统,类似 FB 的 secret page。
  5. 脑洞:可以有匿名的工资爆料,类似 GlassDoor。
  6. 其他一些有意思的东西。

关于同城公司的设计, 期待各位热心朋友的宝贵意见。

create new community

感谢你的关注 !

如果在社区页里找不到你感兴趣的社区,麻烦在下方给我留言, 我会在第一时间内处理。

image

请确保你的请求符合以下要求

  1. 你在社区页面找不到这个社区或类似主题的社区。
  2. 你要创建的社区和IT 行业有一定关系, 包括但不限于: 编程语言/框架、 设计类、教程、工具、AI/区块链, 运维/产品, 科技/前沿 等等。
  3. 可以是同城社区,如果你所在城市不在默认的同城社区之中。
  4. 可以是这个群体普遍使用/感兴趣的主题,比如 "Github", "UI设计", "每日妹子" 等等。
  5. 欢迎补充..

期待各位热心朋友的意见。

An in-range update of pubsub-js is breaking the build 🚨

The dependency pubsub-js was updated from 1.6.1 to 1.7.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

pubsub-js is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 2 commits.

  • 9300bd6 1.7.0
  • c6508f6 Add support for Symbol() as event message (#141)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.