* 'decoupling' of github.com:biosistemika/scinote-web:
fix(AboutScinoteModal): Enable react optimizations
Fix addons display in info modal [SCI-1875]
Set strict version for rubocop gem, because the new one is not compatible with the previously used one. Also updated it to the newest version.
Children generated within a loop or by an iterator need to be passed
a unique `key` property so React can properly watch their updates and
perform the necessary actions.
Signed-off-by: Adrian Oprea <adrian@oprea.rocks>
* 'decoupling' of github.com:biosistemika/scinote-web: (21 commits)
fixes bug in the invitation_controller with full_name sanitization [fixes SCI-1944]
Remove Addons info test from core [SCI-1875]
Remove skip_on_import from repository_cell [SCI-1939]
fixes bug with comment actions dropdown [fixes SCI-1938]
fixes first element in global activities logs[fixes SCI-1866]
Fix task repository row selector [SCI-1940]
Fix repository item export [SCI-1945]
Fix samples import [SCI-1946]
adds first date to _list.html.erb view
Remove Addons caption if no addons in info modal and fix linter packages [SCI-1875]
Fix repository records import [SCI-1939]
Fix export samples button [SCI-1936]
refactor
adds additional tests for permissions controller
fix HOC to recive objects
fixes flow, and before_action in permissions_controller
fixes per @duco 's request
remove unneeded import
add permissions endpoint on the API
fix request
...
It seems like the backend is returning a weird response when queried for
addons. Once the backend issue is identified and fixed this should be
uncommented.
Signed-off-by: Adrian Oprea <adrian@oprea.rocks>
The render hijacking library wash updated to use our own version of
react-traversal. The original library did not provide ES5 build so the
overall app build was failing.
Signed-off-by: Adrian Oprea <adrian@oprea.rocks>
The meta-configuration structure imposes we change the way `react-hijack` parses and pulls its data. Because that work is both error-prone and also time-consuming, we chose to implement a function that would "massage" the data so it fits the current way react-hijack expects it.
- Create variables for the paths the script impacts
- Create a file to host the configuration, import each add-on config and re-export them through a single object
Instead of forcing this knowledge on the add-on, we inserted it here. The benefit is that we are able to point the core to whatever directory we choose, without modifying each addon in turn.
