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

Webpage in master 1 #78

Merged
merged 5 commits into from
Jan 14, 2018

Conversation

stereobooster
Copy link
Collaborator

@stereobooster stereobooster commented Dec 31, 2017

No description provided.

@stereobooster stereobooster force-pushed the webpage-in-master branch 2 times, most recently from 5b98b70 to 618b5bf Compare January 1, 2018 23:32
@stereobooster stereobooster mentioned this pull request Jan 3, 2018
@stereobooster
Copy link
Collaborator Author

stereobooster commented Jan 3, 2018

This is good to merge. What is inside:

  • moved webpage to master
  • deployment with travis-ci
  • some refactoring

TODO: remove webpage branch after merge

@stereobooster stereobooster changed the title Move webpage to master Webpage in master 1 Jan 3, 2018
Copy link
Owner

@MicheleBertoli MicheleBertoli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you very much, @stereobooster.
It looks great overall, I just left a couple of questions/comments.

@@ -0,0 +1,51 @@
#!/usr/bin/env node
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we remove this file from the current PR?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will remove last commit from this PR


const CellTd = options => {
const { header, value } = options;
if (header === "Package") {
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This recurring pattern (if Package else if Version) doesn't seem right.
Do you mind implementing another solution?
Like using a map, or different components.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

const fields = {
    "Package": value => { ... return join(links, " + "); },
    "Version": x => x,
    "default": symbol
}
const field = fields[header] || fields["default"]
return <td>{ field(value) }</td>

}, []);

const symbol = value => {
if (value === true) {
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What are the possible values of value here?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

true, false, undefined

@stereobooster
Copy link
Collaborator Author

@MicheleBertoli done

@stereobooster stereobooster mentioned this pull request Jan 4, 2018
3 tasks
@MicheleBertoli
Copy link
Owner

LGTM, thank you very much @stereobooster.

@MicheleBertoli MicheleBertoli merged commit 3f6e2b9 into MicheleBertoli:master Jan 14, 2018
@MicheleBertoli
Copy link
Owner

Yay 0e680fe
FYI, I had to pass the no-sandbox option to puppeter.
Thank you very much one more time.

@stereobooster
Copy link
Collaborator Author

Probably missed it when was moving a website from one branch to another.

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

Successfully merging this pull request may close these issues.

None yet

2 participants