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

Module names are incorrectly used in HTML step selector in demo #1061

Closed
tech4GT opened this issue May 8, 2019 · 13 comments · Fixed by #1073
Closed

Module names are incorrectly used in HTML step selector in demo #1061

tech4GT opened this issue May 8, 2019 · 13 comments · Fixed by #1073

Comments

@tech4GT
Copy link
Member

tech4GT commented May 8, 2019

The module names while adding them in the demo are wrong, they appear with spaces like "webgl-distort" appears as "webgl distort"
This is causing a critical failure of the demo. (in the main branch -- @jywarren)

=====@harshkhandeparkar=====

Update: this has been fixed by replacing the spaces with hyphens for now but a better, thorough fix would be better

Possible solution:

  1. Modules have a name and an id to reference it. The id has hyphens(and only small letters) and the name has spaces and capitals. E.g.: webgl-distort(id), WebGL Distort (name)

  2. We could assign hidden attributes or jQuery $.data properties to the module selector fields so that we can display the name but use the id for referencing the module name in the sequencer when a step is to be added.

=====@harshkhandeparkar=====

(Update (@jywarren) this was quick-fixed in #1073 but follow-ups included at the bottom of this issue)

Sent from my OnePlus3 using FastHub

Sent from my OnePlus3 using FastHub

@harshkhandeparkar
Copy link
Member

harshkhandeparkar commented May 8, 2019

@tech4GT I was trying to edit the issue body and remove the hyphen and add the space in the module body. I did this from this phone app and unfortunately it adds the footer text.

Sent from my OnePlus3 using FastHub

@jywarren
Copy link
Member

Hi, I wasn't able to reproduce this, I found this to work correctly:

https://sequencer.publiclab.org/examples/#steps=webgl-distort{}

Can you clarify? Thanks!

@tech4GT
Copy link
Member Author

tech4GT commented May 25, 2019

@jywarren I think we already have a pr for this. #1073

@harshkhandeparkar
Copy link
Member

urlHash works but the selector doesn't

@jywarren
Copy link
Member

A gif of the issue would be great. And eventually a UI test!

@jywarren
Copy link
Member

No, I used the selector in the page to get this url, and it worked there too.

@harshkhandeparkar
Copy link
Member

harshkhandeparkar commented May 25, 2019 via email

@jywarren
Copy link
Member

Hi @harshkhandeparkar i know you said you're copying in all the relevant documentation for this bug, but in the meantime I am following the exact steps laid out in the chatroom and was able to reproduce this on the main branch in the demo, running locally:

image

@jywarren
Copy link
Member

Exact issue for reproducing:

There is an issue with the step selection UI on the latest main branch, but not in the gh-pages demo, with modules that include spaces in their names?

To reproduce, the demo can be run locally from the latest main branch, using the "webgl-distort" module

The PR at #1073 substitutes hyphens for spaces (as a quick fix), and @harshkhandeparkar will be copying in suggestions for a more thorough fix here in a moment.

@jywarren jywarren changed the title [URGENT] Module names are wrong [URGENT] Module names are incorrectly used in HTML step selector in demo May 25, 2019
@jywarren jywarren reopened this May 25, 2019
@jywarren jywarren changed the title [URGENT] Module names are incorrectly used in HTML step selector in demo Module names are incorrectly used in HTML step selector in demo May 25, 2019
@jywarren
Copy link
Member

I'd also like to recommend a test for this behavior so we can be sure it doesn't happen in the future! Thanks!

@jywarren
Copy link
Member

Also, published v3.3.3!

@harshkhandeparkar
Copy link
Member

@jywarren suggestions copied in the issue body itself.

@jywarren
Copy link
Member

Closing, but opening a new issue for the tests!

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

Successfully merging a pull request may close this issue.

3 participants