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

fix(files): Remove use of localstorage. #217

Merged
merged 1 commit into from
Jan 24, 2016

Conversation

dignifiedquire
Copy link
Member

As discussed this removes the local tab in favor of the
all and pinned tabs. Also makes the drop area for files
visible at all times.

Closes #32

@jbenet @whyrusleeping please take a look if this is okay for listing files for now or if there are better methods.

@whyrusleeping
Copy link
Member

I think thats good for now. It would be cool to list things inside ipfs files in the future

@dignifiedquire
Copy link
Member Author

@whyrusleeping why don't you open an issue for that :P

@jbenet
Copy link
Member

jbenet commented Jan 21, 2016

How does it list all? ipfs refs local ?

@jbenet
Copy link
Member

jbenet commented Jan 21, 2016

👍 for removing local storage

@dignifiedquire
Copy link
Member Author

@jbenet this is how it does it currently:

(that was like this before) would refs local be better? What's the exact difference?

As discussed this removes the local tab in favor of the
all and pinned tabs. Also makes the drop area for files
visible at all times.

Closes #32
@dignifiedquire dignifiedquire force-pushed the fix/remove-local-storage branch from ab31d4a to c3d04b5 Compare January 22, 2016 11:42
@jbenet
Copy link
Member

jbenet commented Jan 24, 2016

this is fine i think

@jbenet
Copy link
Member

jbenet commented Jan 24, 2016

  • a files tab may want to list the ipfs files root
  • i havent looked extensively at the code-- @diasdavid maybe?

@jbenet
Copy link
Member

jbenet commented Jan 24, 2016

LGTM from a UX perspective

@@ -33,36 +31,53 @@ default class Files extends React.Component {
clearInterval(this.pollInterval)
}

getFiles = () => {
getFiles () {
Copy link
Member

Choose a reason for hiding this comment

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

isn't there a missing = and => here, even if just for consistency

Copy link
Member Author

Choose a reason for hiding this comment

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

No, the important part is that these are two different sorts of methods, if you declare them like this:

getFiles () {
}

it's a regular method. If you declare it like this:

getFiles = () => {
}

it means that in addition it is bound i.e. getFiles = getFiles.bind(this) where this is the instance of the class.

As this method is not used passed somewhere there is no need to bind it.

@daviddias
Copy link
Member

Other than the one comment, LGTM :) nice!

dignifiedquire added a commit that referenced this pull request Jan 24, 2016
fix(files): Remove use of localstorage.
@dignifiedquire dignifiedquire merged commit afe9b13 into master Jan 24, 2016
@dignifiedquire dignifiedquire deleted the fix/remove-local-storage branch January 24, 2016 18:28
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

4 participants