-
-
Notifications
You must be signed in to change notification settings - Fork 281
[WIP] final query scheduling fixes and testing #500
Changes from 17 commits
bf2d0d1
044a866
4771514
842dd96
db76145
601196c
a13fd98
96005d4
d696973
f8e7485
aa4548a
2ba6cee
fa05078
631d4a6
82c4d56
f53ddfc
ddd18e1
0bf0b95
75cb763
01572d5
d20fc70
187aad4
2817b2a
00ce988
8c92585
391bd5a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -15,7 +15,10 @@ const PromptLoginModal = props => ( | |
× | ||
</button> | ||
<Row className="header"> | ||
<p>To create a scheduled query, you'll need to be logged into Plotly.</p> | ||
<p> | ||
To create a scheduled query, you'll need to be logged into Plotly. Logging in will reset your query, | ||
so please save it elsewhere before doing so. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is probably about as good as we can do I suppose. There's no way to squirrel the query away into local storage or a cookie or something and restore it after login? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Happy to look into this on the next stage, but given time constraints, I don't feel comfortable implementing/testing this functionality before the release. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. OK. Any way we could make this warning very clear? put it on its own line, in bold? this is a pretty bad failure case if you've just iterated for an hour on some complex query. |
||
</p> | ||
</Row> | ||
<Row> | ||
<button type="submit" className="submit" onClick={props.onSubmit}> | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't debugged the reason, but this isn't working for me. I'm still able to create queries without a name:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That’s by design I think...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Er... perhaps not, looking at the code. I should have said “I had assumed it was by design that you can create queries without names and it didn’t bother me”
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, it looks like you can create queries named
""
but not" "
... The first part of theif
condition is falsey for""
. Given that we still have to support unnamed queries, we may as well just trim and move on if the user tries" "
instead of complaining :)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@briandennis How about
if ((this.state.name || '').trim().length === 0)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My preference here would be to allow any trimmed string, even empty ones, but I'm also OK with the current behaviour if we're out of time.