ifactory-solutions/inside-client

Human Resources Department Tool. https://ifactory-solutions.github.io/inside-client/

inside-client's Issues

Add ant design

Configure commit lint

Maybe we could use this lib: https://github.com/marionebl/commitlint

Create CONTRIBUTING.md file

• Search about how open source projects allow contribution
• Propose guidelines for contributions to the project

Gitbook

Add gitbook to the project. example

Finish login feature

Allow access to any page only if user is logged in. Login feature is done on inside-server.

Proposal of a README.md Template Model

I've been searching for good and clean readme.md templates for open source projects. Bellow is the one I found more interesting. What you guys think?

https://gist.github.com/PurpleBooth/109311bb0361f32d87a2

Add Internationalization

• Add Internationalization
• Add Basic tests

Create Employee integration with backend

Create Login Page Layout

Create login page based on ant design patterns

Define basic flow to create new pages on application

The goal is to define a basic flow to create new pages on client side the application.

Jira:
http://jira.ifactory.com.br/browse/IFACTORYCOLLAB-4

Basic flow:

1. List - cards or grid
2. Creation
3. Edition
4. Visualization detailed information

For example:

• to create a new page is it required open a dialog with form or open a new page?

Configure automatic Changelog generation

We could use auto changelog generation which follow the Conventional Commits Specifications and #2 .

e.g. this guy: https://github.com/conventional-changelog/standard-version

Add .gitattributes file

Atteding to @Jefferson227 comment on #8, the end-of-line normalization should be handled with .gitattributes file. Setting * text=auto as default behavior to automatically normalize line endings, which is mentioned on git docs.

Add .editorconfig

something like this: https://github.com/gitpoint/git-point/blob/master/.editorconfig

List Employees integration with backend

requestAnimationFrame warning with React 16

Expected Behavior

No more warnings

Current Behavior

when execute npm test

console.error node_modules/fbjs/lib/warning.js:33
  Warning: React depends on requestAnimationFrame. Make sure that you load a polyfill in older browsers. http://fb.me/react-polyfills`

Possible Solution

1. jestjs/jest#4545 (comment)
2. https://gist.github.com/gaearon/9a4d54653ae9c50af6c54b4e0e56b583#gistcomment-2226297
3. jestjs/jest#4545 (comment)

Steps to Reproduce

execute npm test

Context (Environment)

Test

Create Issue template

Add Gitter badge to README.md

Create Employee Layout

• Refactor create employee page with more data.
• Validate form data
• Create unit tests

Commit message conventions

Let's try? What are some thoughts on this subject?

Useful links to explore:
https://conventionalcommits.org/
https://github.com/kazupon/git-commit-message-convention
https://github.com/marionebl/commitlint

Refactor code to allow SASS instead of only CSS

Create Login page

• Login page Layout
• Login Integration with apollo
• Login tests with jest

Create profile layout

• Create layout
• Create tests

Update project to use react 16

Configure eslint

Add Redux

Eject react app project

Add inside logo to github readme

Get the logo with @lucasazevedoqx

Create vacation list

• Create basic layout
• Create basic tests

Add Content to Wiki - Explain how commit messages works

Since we are going to use commitlint and husky to avoid 💩 commit messages it would be good to explain how our commit messages should be formatted.

Please add on our wiki how that works based on the rules added to the commitlint file(commitlint/index.js).

Add Continuous Integration

Implement the application with accessibility in mind

Guys, as this is an open source project I think we should keep accessibility in mind when developing the whole app, mainly the frontend. Providing users with accessibility options widens the potential audience of the software, and should exist as a common practice in all software design and production. What are your thoughts about this topic?

Configure automated code review

Hi, guys!
What do you think about adding an automated code review to the project? I'm currently using Codacy on personal projects. It helps me a lot. It uses ESlint rules and some other that they detect automatically depending on what languages your project is using. Security issues, Erro prone, complexity, code coverage, project quality (we already have it on tra1vis).
Integration with Github and Slack as well.
Free for open source projects

For more details: https://www.codacy.com/features

Create loading component

• Create loading component
• Create tests

Add React Router

Create landing page

Create landing page like(ideas):

• http://www.pontomais.com.br/
• https://runrun.it/pt-BR
• https://coursify.me/

Create medical certificate list page

• Create layout
• Create tests

Integrate List projects page with server

• Implement projects list page with redux and redux saga