Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dayModel.js -> rendererFunc () #39

Closed
3 tasks done
atherdon opened this issue Jun 29, 2018 · 3 comments
Closed
3 tasks done

dayModel.js -> rendererFunc () #39

atherdon opened this issue Jun 29, 2018 · 3 comments
Assignees

Comments

@atherdon
Copy link
Member

atherdon commented Jun 29, 2018

  • first
if(item%50 === 0) {
                if(topToDown[index+1] === buffer[i].start) {
                    return (
                            <ListGroupItem style={fillerBlockHeight} key={item}></ListGroupItem>
                    );
                }
                return (
                        <ListGroupItem style={defaultBlockHeight} key={item}></ListGroupItem>
                );
            }

as you can see - we have a similar return, just a different an attribute.
i think we can improve it and return this Tag only once, but in different conditions


  • second
{this.rendererFunc(data[this.props.index])}
does we're really need to pass that data in render()?

  • third
for(var traverse = 0; traverse <= 900; traverse +=25) {
            topToDown.push(traverse);
            if(buffer[i].start === traverse ) {
                traverse += buffer[i].height - 25;
                if(i < buffer.length - 1){
                  i++;
                }
            }
        }

Use underscore for simplifying code here

@atherdon
Copy link
Member Author

#47

sanchit94 added a commit that referenced this issue Jun 30, 2018
sanchit94 added a commit that referenced this issue Jun 30, 2018
# This is the 1st commit message:

small changes, to organise the code.

# This is the commit message #2:

Removed unused files

# This is the commit message #3:

Added routers and fixed warning messages

Fixes #34 and #48 , and partially #39
sanchit94 added a commit that referenced this issue Jun 30, 2018
small changes, to organise the code.

Removed unused files

Added routers and fixed warning messages

Fixes #34 and #48 , and partially #39

upd

upd

upd

Fixed minor bugs
@atherdon
Copy link
Member Author

atherdon commented Jul 1, 2018

can we close it, right?

@sanchit94
Copy link
Collaborator

Yea, you can check the code and close!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants