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.

Sign up for GitHub

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

Jump to bottom

Report type with multiple spaces broke the menu bar #207

Closed
richard-julien opened this issue Sep 2, 2019 · 0 comments
Closed

Report type with multiple spaces broke the menu bar #207

richard-julien opened this issue Sep 2, 2019 · 0 comments
Assignees
@richard-julien
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone
Release 1.1.2

Comments

@richard-julien
Copy link
Member

Description

Report type with multiple spaces broke the menu bar

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Rename a report type with multiple spaces
  2. Go to reports page
  3. Click on the report type you created

Expected Output

Menu bar displayed correctly

Actual Output

No menu bar
@richard-julien richard-julien self-assigned this Sep 2, 2019
@richard-julien richard-julien added the bug use for describing something not working as expected label Sep 2, 2019
@richard-julien richard-julien added this to the Release 1.1.2 milestone Sep 2, 2019
richard-julien added a commit that referenced this issue Sep 2, 2019
@richard-julien
Fixing #207 in the context of the branch review
00af555
richard-julien added a commit that referenced this issue Sep 2, 2019
@richard-julien
Fixing #207 in the context of the branch review
2659d12
SamuelHassine pushed a commit that referenced this issue Sep 2, 2019
[schema] Remove the UserTargetsRule and fix reports top bar behavior (#…
d168b1c 
…202, #207)

* [schema] Remove the UserTargetsRule (#202)
* [frontend] Fix the reports context when saving parameters of list in local storage
* Fixing #207 in the context of the branch review
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Sep 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@richard-julien richard-julien

Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Milestone
Release 1.1.2
Development

No branches or pull requests
2 participants
@richard-julien @SamuelHassine