Skip to content

feat(upload): added upload functionality#47

Open
daniel-lanciana wants to merge 14 commits into
ConsenSysMesh:masterfrom
daniel-lanciana:add-upload-tab
Open

feat(upload): added upload functionality#47
daniel-lanciana wants to merge 14 commits into
ConsenSysMesh:masterfrom
daniel-lanciana:add-upload-tab

Conversation

@daniel-lanciana

Copy link
Copy Markdown
Contributor

Based on consensys.github.io/linnia-faucet (plus some general refactoring/cleanup).

@daniel-lanciana

Copy link
Copy Markdown
Contributor Author

One small thing I couldn't figure out quickly was how to prevent all inputs from being uppercase -- this is confusing (e.g. JSON appears to be uppercase, but on retrieval is lowercase)..

@MaxBlaushild MaxBlaushild left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code looks great! Just two questions about requirements, then looks good to me

Comment thread src/components/Upload.js Outdated

handleSubmit = (event) => {
event.preventDefault();
const file = JSON.parse(this.state.file);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Dispatch an upload error here if file is un-parsable? Most people (myself included) suck at hand rolling json so I imagine this will fail a lot

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Done, moved validation further downstream to the action.

Comment thread src/components/UploadForm.js Outdated
/>

<Typography variant='body1' className={classes.paragraph}>
<b>Metadata</b> should be text that people will use to find your data. What will be useful to query later?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

We're very strongly encouraging metadata to be stringified JSON now. Would be nice to update the copy/add a check to ensure that the metadata is parseable JSON.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Done, included the sample metadata and a link to the guidelines.

@daniel-lanciana

Copy link
Copy Markdown
Contributor Author

@MaxBlaushild only thing left is my previous comment about how to stop inputs from being forced uppercase..

@daniel-lanciana

Copy link
Copy Markdown
Contributor Author

@MaxBlaushild isolated the uppercase issue as the linnia-brand ThemeProvider font Heavitas, which only has uppercase typeface. This threw me off as I was looking for uppercase CSS styling! Thoughts on changing the font for inputs to allow lowercase?

@MaxBlaushild

MaxBlaushild commented Oct 3, 2018

Copy link
Copy Markdown
Contributor

@daniel-lanciana Aha! That's probably something we should have noticed sooner 😅

Raleway is the common font that our material-ui theme uses. I'm loath to change it in the branding module itself, since we're currently undergoing a rebrand and will be changing the font soon enough anyways, so I feel like the best solution would just to be to override the font using the material-ui component API https://material-ui.com/api/text-field/ to raleway

@daniel-lanciana

Copy link
Copy Markdown
Contributor Author

@MaxBlaushild added a global CSS style for textarea inputs to use 'Raleway' instead.

@MaxBlaushild

Copy link
Copy Markdown
Contributor

Thanks Daniel! Looks good to me

@godfreyhobbs godfreyhobbs self-assigned this Dec 29, 2018

@godfreyhobbs godfreyhobbs left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@daniel-lanciana thanks for taking an interesting with our project. Unfortunately, this pull request does not align with our long-term goals. Based on our user's feedback the stow-box is too complex with too many files. The stow box should be a very simple start kit that can be quickly grokked in full.

Therefore we want to remove functionality rather than add functionality.

I suggest making this a new repo that can be an advanced sample stow application.

Let me know if you have any questions.

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.

4 participants