Giter Site home page Giter Site logo

Comments (5)

brauliodiez avatar brauliodiez commented on July 24, 2024 1

Take as well the one about using same names fornthe imports.

This three tasks are heavy because we need to propagate them to all the samples plus test that we havent broken anthing.

On the other Hand it will enhance code readibility

Sent from my Windows Phone

-----Mensaje original-----
De: "[email protected]" [email protected]
Enviado: ‎19/‎03/‎2016 12:27
Para: "Lemoncode/react-typescript-samples" [email protected]; "Lemoncode/react-typescript-samples" [email protected]
Asunto: RE: [react-typescript-samples] Code cleanup study (#30)

Lets start with the first two items in the list

Sent from my Windows Phone

De: Antonio L. Gil
Enviado: ‎19/‎03/‎2016 12:06
Para: Lemoncode/react-typescript-samples
CC: Braulio Diez
Asunto: Re: [react-typescript-samples] Code cleanup study (#30)

I add more items to list.
Must change:
FireValidationFieldVallueChange to FireFieldValueChange
Remove unnecessary imports (e.g. memberapi on reducers).
Unifying variable names in imports (e.g. Sometimes we write 'memberAPI' and in other cases we write 'MemberAPI'. In my opinion, in this case we should write in camelCase due to a new instance is created when it's exported. In other case should be in PascalCase.
Change tabs to 2 spaces characters for indentation and reformat code. For this, I recommend using tslint.json file.
Fixing syntax of properties in several interfaces. Change ',' for ';' and putting in the end of the property name.
To be discussed:
Avoid export default and import classes with curly-bracket {}
Separate presentationales from container.
Create a enum / const like class for actions types..

You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

from react-typescript-samples.

antoniogiroz avatar antoniogiroz commented on July 24, 2024

Sounds good. I will work on it

from react-typescript-samples.

brauliodiez avatar brauliodiez commented on July 24, 2024

Let's start giving here ideas, and then compile them:

Must change:

  • FireValidationFieldVallueChange to FireFieldValueChange
  • Remove unnceseary imports (e.g. memberapi on reducers).

To be discussed:

  • Avoid export default
  • Separate presentationales from container.
  • Create a enum / const like class for actions types..

from react-typescript-samples.

antoniogiroz avatar antoniogiroz commented on July 24, 2024

I add more items to list.

Must change:

  • FireValidationFieldVallueChange to FireFieldValueChange
  • Remove unnecessary imports (e.g. memberapi on reducers).
  • Unify variable names in imports (e.g. Sometimes we write 'memberAPI' and in other cases we write 'MemberAPI'. In my opinion, in this case we should write in camelCase due to a new instance is created when it's exported. In other case should be in PascalCase.
  • Change tabs to 2 spaces characters for indentation and reformat code. For this, I recommend using tslint.json file.
  • Fixing syntax of properties in several interfaces. Change ',' for ';' and putting in the end of the property name.
  • Unify string quotes. Use single quotes ' or double quotes but not both. The typescript coding guidelines by Microsoft proposes to use doble for strings: https://github.com/Microsoft/TypeScript/wiki/Coding-guidelines

To be discussed:

  • Avoid export default and import classes with curly-bracket {}
  • Separate presentationales from container.
  • Create a enum / const like class for actions types..

from react-typescript-samples.

brauliodiez avatar brauliodiez commented on July 24, 2024

Lets start with the first two items in the list

Sent from my Windows Phone

-----Mensaje original-----
De: "Antonio L. Gil" [email protected]
Enviado: ‎19/‎03/‎2016 12:06
Para: "Lemoncode/react-typescript-samples" [email protected]
CC: "Braulio Diez" [email protected]
Asunto: Re: [react-typescript-samples] Code cleanup study (#30)

I add more items to list.
Must change:
FireValidationFieldVallueChange to FireFieldValueChange
Remove unnecessary imports (e.g. memberapi on reducers).
Unifying variable names in imports (e.g. Sometimes we write 'memberAPI' and in other cases we write 'MemberAPI'. In my opinion, in this case we should write in camelCase due to a new instance is created when it's exported. In other case should be in PascalCase.
Change tabs to 2 spaces characters for indentation and reformat code. For this, I recommend using tslint.json file.
Fixing syntax of properties in several interfaces. Change ',' for ';' and putting in the end of the property name.
To be discussed:
Avoid export default and import classes with curly-bracket {}
Separate presentationales from container.
Create a enum / const like class for actions types..

You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

from react-typescript-samples.

Related Issues (20)

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.