jira_clone VS bookshelf

A couple other open source repos I think are great are: - RocketChat - React Jira clone

No worries man, there’s a bunch of good ones - https://github.com/taniarascia/takenote - https://github.com/karlhadwen/todoist - https://github.com/oldboyxx/jira_clone - https://github.com/getsentry/sentry

Hey check out this repo: https://github.com/oldboyxx/jira_clone

Another possible way is to structure your folders is to have one per feature/context, let's say Auth, Posts, Videos, Projects etc. You can then have everything related your feature in that folder: like Post.jsx, Post.test.jsx, styles.jsx and index.jsx as the entry point of the feature. Look at this repo for this sort of(-ish) approach: https://github.com/oldboyxx/jira_clone/tree/master/client

Check out jira clone.

Here is a good example of react application https://github.com/oldboyxx/jira_clone. It's a Jira clone and the code is clean and simple to understand.

SEEKING WORK | Central Europe(EU, CET+0) | Remote | https://getivor.com

I'm a seasoned web development expert with a knack for UX design. I specialize in front-end(React), but also do back-end(Node).

I have extensive experience in architecting, building, and delivering large custom-made web applications.

Over the last decade I helped several US/EU based clients build Airbnb-like platforms, real-time GPS vehicle tracking suites, healthcare/finance/construction apps, and more.

I mostly collaborate with tech companies, but also have a lot of positive experiences assuming CTO-for-hire roles to work with non-technical founders.

Tech stack: React.js, JS/TypeScript/Babel, Node, Webpack, GraphQL, ESLint, Cypress.io, styled-components etc.

• Read more on my website: https://getivor.com

• View recent project - Jira Clone (6,4k stars): https://github.com/oldboyxx/jira_clone | Live demo: https://jira.ivorreic.com

• Passion project from 2014 (100k monthly visitors): https://movieo.me/movies

RATE: $150/hour with a minimum budget of $30k.

Get in touch: [email protected]

Thực hành dựa trên source code

If you're looking for one with good tests, I'd check Kent C. Dodds bookshelf

Keep your high-level screens in a folder called screens/pages. Reusable/lower level components in a separate folder (called components). Utils/shared folder for shared utlity functions/hooks etc. For tests, you can have a tests folder to store tests. Look at this repo for reference: https://github.com/kentcdodds/bookshelf

When a function gets too long and confusing, a good thing to do is to split it up into several shorter, more focused functions. We will likely have more asynchronous tasks to perform in other components, so let's first extract the logic for handling loading, error, and success states to its own function. (The following was inspired by this.)