boemska / create-sas-app Goto Github PK

Implement optimized file rename where only the metadata is changed. Implement folder rename

Implement project properties page with share project feature

First of all we are very enthusiast about your work you have done, but when we try to retrieve our reports they did not show. Only reports that showed were .sas files

the text in the images are in dutch

As you can see in the images above, in Viya it shows 3 reports which 1 is a Sas-Report file and the other 2 are .sas files. But it only shows the .sas files in your app.

How can we fix this?

Secondly how can we show diagrams/graphs in reports like you did in this video: https://vimeo.com/431629954?

Thank you for reading our question.

Easy change in setupProxy w/ secure: false, but will need to replace xhr2 in the config script with something that doesn't mind invalid certs

Implementation of projects load on onsen seed.

Fluentui - Implement projects list with folder structure (breadcrumb)

I think this will be nice to do for users with the use case described in #10, and showcase the VA SDK integration.

Steps to reproduce

1. Open projects list
2. Select project from list
   - At this point you are on Project Properties page of last selected project
3. Rename project (Save changes)
   - Project is ‘modified’
4. Go back to projects list
5. Select another project
   - You will see Dialog with question for proceeding (Enter ‘Cancel')
6. After ‘Canceling’ , you will be redirected to 'Project Properties' page of previous modified project
   (as expected)
7. Go back to the projects list. If you try to open the same project as last time (not the currently
   modified unsaved project), you will be redirected without asking for proceeding.

In the projectProperties reducer when a change is saved the new modifiedSince timestamp isn't in any way saved to local storage, this way when the page is reloaded the values that the reducer gets from the localstorage has an outdated timestamp

This is a placeholder to track integration of @devaKumaraswamy's excellent restaf + restaflib into CSA, as an enhancement to our own managedRequest API access mechanism.

Looking at the authentication options it should be possible to configure axios with an intereceptor to pause requests while re-authentication happens, and I quite like the idea of moving h54s to axios in general for the next version - it does a lot of things elegantly which we implemented from scratch within h54s (because axios didn't exist at the time).

We need to think about how we best do it - whether to just include restaf here as a branch that we integrate with the login screen and keep the current auth + keepalive mechanisms, or wait until h54s v3 where we can share axios with restaf. Just putting this out there for now.

Redesign onsen architecture in way to provide push/pop mechanism. Everything will be organized around tabbar page which will be entry point in the app.

Opening this issue to track that upstream dependency and wait for the PR at /facebook/create-react-app #5369 to be merged.

Currently we're using react-app-rewired and react-app-rewire-workbox to enable customisation of our service worker config, so we can control the offline mode, update and caching behaviours without ejecting. This won't be needed once that PR is merged and we can get rid of the dependency on react-app-rewired.

I know we have this in the h54s repo, but I think we need everything in one place. Either we should write comprehensive instructions on configuring things like project document roots, metadata roots and services, or build it into the CSA yarn run configure script.

When new version of app get released app should show notification to user.
On page refresh new version should be applied