Skip to content

[jsx/Markdown.js] Markdown feature bullets#5542

Closed
maltheism wants to merge 38 commits into
aces:majorfrom
maltheism:master_markdown_feature_bullets
Closed

[jsx/Markdown.js] Markdown feature bullets#5542
maltheism wants to merge 38 commits into
aces:majorfrom
maltheism:master_markdown_feature_bullets

Conversation

@maltheism

@maltheism maltheism commented Nov 5, 2019

Copy link
Copy Markdown
Member

Brief summary of changes

Adds Markdown "bullets" which is the equivalent to unordered html list.

  • First implementation of the bullets to the unordered html list (feature). I couldn't think of a way to do this with regex.
  • I'm not happy with the first attempt because it only works with single list. Next implementation need to make the function recursive for lists within a list. Although I thought it would be good to send a PR for now.

Testing instructions (if applicable)

  1. Make a markdown file inside help for one of the modules with bullets.
  2. View on the frontend.

Links to related tickets (GitHub, Redmine, ...)

driusan and others added 30 commits June 5, 2017 16:03
Update master to the latest LORIS release.
[POST RELEASE] PULL FORWARD OF 20.0.0 INTO MASTER
…master

PUSH FORWARD of the v20.0.2 RELEASE INTO THE master branch
PUSH FORWARD OF THE 20.2.0 RELEASE TO MASTER
Allows the install script to continue if the command "hostnamectl" is not found.
…s were allowed to see statistics from sites they don't have access to. (aces#5315)

A user with role Data Entry was able to see demographic statistics from sites it does not belong/have access

For example if there are two users and two sites:
user Site 1 is associate only to Site_1.
user Site 2 is associate only to Site_2.

(Both of them have the role Data Entry and nothing more in the permissions)
When going to MainMenu->Reports->Statistics->Demographic Statistics
The user of Site 1 is able to see the statistics for Site 2 and vice versa

Now each user should be able to see only the demographic statistics for the sites it belong/have access

Fixes aces#5086
When clicking on the breadcrumb in Candidate Parameters, the CandID was not being included in the link and thus was throwing a 500 error (specifically in the Consent Status tab).
… - bugfix (aces#5203)

Add this [Run make (for production instances) or make dev (for development sandboxes). ] into readme

to help solve issue aces#5197
related to aces#5198
Resolves aces#3946
"ConfigException" doesn't exist and is causing LORIS to crash (for the wrong reason) when an exception is thrown.
…re allowed to see imaging statistics from sites they don't have access to. (aces#5339)

A user with role Data Entry was able to see imaging statistics from sites it does not belong/have access

For example if there are two users and two sites:
user Site 1 is associate only to Site_1.
user Site 2 is associate only to Site_2.

(Both of them have the role Data Entry and nothing more in the permissions)

When going to MainMenu->Reports->Statistics->Imaging Statistics

The user of Site 1 is able to see the imaging statistics for Site 2 and vice versa.
…nistration field aces#5367

Date of administartion min and max year are currently hard-coded, but should use the config values of study start and end date.

Resolves aces#5361.
There was a slight issue with the logic during the install process that swallowed a DB exeption in favour of returning false; however, the return value of this function was never checked so the code kept trying to function without a DB connection. This could give a 500 error in some cases, making the install look messy and hard to debug.
When ajax/datadictionary.php is called, Notices are generated when the category or key params are checked when not present in the request. Add isset check to avoid them.
…ces#5205)

Clean up install script and instruct user's to run make [dev] after.
@maltheism maltheism added the Category: Feature PR or issue that aims to introduce a new feature label Nov 5, 2019
@maltheism maltheism requested a review from driusan November 5, 2019 19:41
@johnsaigle johnsaigle added the Area: UI PR or issue related to the user interface label Nov 5, 2019
@ridz1208

ridz1208 commented Nov 6, 2019

Copy link
Copy Markdown
Collaborator

if this is not a bugfix please base it on major for now as it will only be part of the next release

@ridz1208 ridz1208 added the State: Needs rebase PR that needs to be rebased to proceed (conflicts, wrong branch...) label Nov 6, 2019
@maltheism maltheism changed the base branch from master to major November 12, 2019 18:51
@maltheism

Copy link
Copy Markdown
Member Author

I messed up the rebase @ridz1208 :(
See #5615 for the new PR on major

@maltheism maltheism closed this Nov 12, 2019
@christinerogers

christinerogers commented Nov 13, 2019

Copy link
Copy Markdown
Contributor

@ridz1208 These markdown bullets should be a 22-release bugfix PR since existing bullets in the Help text are busted, and are being removed (undesirably) as @knoll-alex does a big update across all modules this week.
So far they're being removed from the Help text just because the markdown bullets are buggy. If they can be fixed/kept for 22, that's ideal.
cc @maltheism

@maltheism maltheism deleted the master_markdown_feature_bullets branch May 24, 2020 02:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area: UI PR or issue related to the user interface Category: Feature PR or issue that aims to introduce a new feature State: Needs rebase PR that needs to be rebased to proceed (conflicts, wrong branch...)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants