factlist/factlist-ui

factlist-ui

Installation

npm i

Development

npm start

Production

npm run build

factlist-ui's Issues

Private Topics

Links can be re-ordered according to "order" attribute in DB.

User page

https://app.zeplin.io/project/5c30b8b553fb07af7d8b2ee7/screen/5d15d045bb617d1af0ccf691
https://app.zeplin.io/project/5c30b8b553fb07af7d8b2ee7/screen/5d15d04352d54e73937204c6
https://app.zeplin.io/project/5c30b8b553fb07af7d8b2ee7/screen/5d15d0431a1c76570698b1d2

Import links

Users should be able to import links (w/tags) from a topic to their own topics.

Loading indicator

Topic editor: Tag autocomlete z-index problem

Aktif linkin z-indexine diğer linklerinkinden yüksek bir değer vererek aşabiliriz ancak ciddi logic gerekir. Sorting kütüphanesi değiştirmek de alternatif bir çözüm olabilir, belki.

Delete deprecated components

Since Factlist is not a fact-checking product anymore, some components and related containers/scenes should be deleted. These components are:

• Claim
• Evidence
• Linkify
• Status
• MultimediaInput
• Attachments

File or link preview boxes for upload

Clone/fork a topic

Refactor styles

Problems:

• Shitload of duplication in styles
• Lack of a consistent style system and proper abstractions (in either CSS classes or components)
• Lack of a theme and sensible theme variables

Authentication/Login status

Authentication ve login status'u icin duzenlemeler yapilmali.

Kullanici login olduktan sonra kullanici bilgilerini API'dan cekmek gerek.
Oner graphQL'e getUserById query methodunu ekledi, boylece onceden yapamadigimiz authenticate olduktan sonra kullanici id'si ile kullanici bilgilerini alma islemini artik yapabilecegiz.

Topic - Homepage view state

https://redpen.io/qu47eaacca42daec88

design profile card

finalize widget design

Searching and filtering

Migrate redux to apollo

Integrate create topic UI

Refactor topic

Topic is mostly working fine but let's adapt it to comply more with React conventions. (e.g. We can probably "lift the state up" instead of relying on context)

Also implement queries with react-apollo's graphql higher order component instead of using the Apollo client directly.

Another thing is that the TopicForm should probably be a dumb component which don't actually make the requests. It should be the parent scene who does that.

https://reactjs.org/docs/lifting-state-up.html

Write docs for adapters and important libs

There are example usages of each adapter in the repo but we need to explicitly document them in order to make it easy for everybody to contribute.

Let's create a "docs" directory and start working in it.

Topic Component CRUD

Create/Edit:

• Add/remove new links
• Add/remove tags of a link (w/autocomplete)
• Sort links between each other
• Update the title of a link.

Delete:

We just need a simple confirmation dialog.

Notes:

• Changes should be sent in a single HTTP request if possible.
• Link metadata should be fetched from link metadata endpoint. It was already implemented in the old API (http://alpha.factlist.com:81/api/v1/embed/?link=http://google.com) @onerciller will add this endpoint to new API with favicon_url attribute. : )

Create Topic Page - UI Styling

Create Link

• "Add a link to your topic" yazisina tikladiginda input alanina link yazilabilecek,
• Blur eventi tetiklendiginde veya enter'a tiklandiginda link kaydedilecek,
• Link silme backend'de hazir, ui'da delete icin tasarima karar verildiginde yapilacak.

Refactoring

Clean up legacy/unnecessary code and dependencies.

refactor for consistency

Kill the Rebass grid

We can definitely survive with standard flex configurations in plain CSS files.

Or we can define our own simple Flex components instead of depending on an external CSS-in-JS solution; if we absolutely want it that way. Not very hard.

Implement global styles

border-radius: 2px;
border-color: #E6E8EB

color-green: #34A08D
color-black: #000000

header{
max-width:1040px;
}
topic{
max-width:630px;
}

Tag page

https://app.zeplin.io/project/5c30b8b553fb07af7d8b2ee7/screen/5d15d0427d1b12733fa3e641
https://app.zeplin.io/project/5c30b8b553fb07af7d8b2ee7/screen/5d15d04352d54e73937204c6
https://app.zeplin.io/project/5c30b8b553fb07af7d8b2ee7/screen/5d15d0431a1c76570698b1d2

Migrate Auth to the new API

Functions:

• Login with Email
• Login with Twitter
• Signup with Email
• Signup with Twitter
• Password reset request
• Change passport section

Form validation errors

New topic take two

• New design (https://app.zeplin.io/project/5c30b8b553fb07af7d8b2ee7/screen/5c423e4f40cdef385c1fb35b)
• Topic title writing bug (funny bug, try and see)
• Link title should be editable
• Link sorting
• Link validation (is it a properly formatted link?)
• Make sure that the topic title is correctly populated
• Proper error handling everywhere with nice user feedback
• Proper React implementation (a bit awkward implementation at the moment)
• Link/tag deletion not working

Kill CRA and switch to Parcel

CRA is uncool, bloated, slow, and unneeded when Parcel exists.