evoluteur / evolutility-ui-react Goto Github PK

In any model collections is the specification of a child set. It is used on a browse screen to retrieve a list of child records displayed in master-detail format.

The fields information is redundant. It matches exactly the fields information in the child model, and can be retrieved as needed by accessing the child model (filtered presumably on inMany). For similar reasons the table and column attributes are also redundant.

Evolutility-server-node changed data format for Stats w/ version 0.8.1.

Hello,
can Evolutility-UI-React to be used with .net api from http://www.evolutility.org ? If not how complicated is to re-write backend evolutility-server-node to c# api?
If all features from http://www.evolutility.org/product/features.aspx supported in Evolutility-UI-React ?

The error is:
Error: ENOENT: no such file or directory, stat 'D:\MyDocs\dev\Evolutility\evolutility-ui-react\src\public\index.html*.css'

Apparently caused by having moved the server.js. Changes required:

res.sendFile(path.join(__dirname, '../public', 'index.html'))

Also

app.use(express.static(path.join(__dirname, '../public')))

The command line in package.json says "run server.js" but the file has been move, so should be "run src/server.js".

To reproduce,

• click on Todo. Displays the list.
• click on Title. Shows up arrow in the title bar.
• click on Title. Shows down arrow in the title bar and sorts list in descending order.
• click on back button. Display does not change (still descending). However, address bar now shows:
  http://localhost:8080/todo/list?order=title.asc
• click on Refresh. Display now shows ascending order.

As a side note, the title bar arrow does not always show correctly.

Hi Olivier,

When clicking the Edit button I saw that the fields that contain dates get erased.
I have attached a printscreen for this below (create_date). The fields had values prior to clicking on the Edit button.

Do you know if there is a particular reason for this? Is it possible to change the logic so that the fields stay as is?

Thank you!
Costin V.

The new version 0.2.0 has a package-lock.json, for the first time AFAIK. It contains a mixture of http: and https:, which is undesirable in its own right, but also causes a heap of regressions when updating from an earlier version in which the file was locally generated.

My guess is that the simplest solution is not to include this file in the release.

For List and Cards views.
Must also fix regression for Charts empty state.

All dates displayed by Evolutility seem to be in US format (mm/dd/yyyy).
The culprit code appears to be this line in format.js:64.

return dateParts[1]+'/'+dateParts[2]+'/'+dateParts[0];

It really does need to format dates according to national preferences (mine are European dd/mm/yyyy).

I just meet you ten minutes ago ,by node-red ant it's tab 'low-code' ,searched your project.
we are too many sames ,so i think you are a kindhearted man too ~ haha

A local storage implementation is a really nice thing, both as a demo and for personal use. The steps I would take are:

• refactor all references to axios into a separate function/object-based API
• create a local storage based implementation of that API.

But maybe there is an easier way, reusing the backbone model from the jQuery project.

I have just been notified by my system that there is a known threat called Trojan:JS/CoinMiner that was introduced in the NodeJS flat-map-stream library.

More details here: hugeglass/flatmap-stream#2.

I would suggest that anyone with this module installed should delete it and reinstall.

No need to add a property, just a function such as isRightJustified(type) and a corresponding style.

React can pass through API calls using a 'proxy' feature.

In package.json:

"proxy": "http://localhost:2000/",

In config.js

apiPath: '/api/v1/',
filesUrl: '/pix/',

See https://www.fullstackreact.com/articles/using-create-react-app-with-a-server/ for some discussion, and a tutorial that nearly works!

For deployment to node hosting such as Heroku etc I think a few things are needed, such as

• ui-react SPA statically loadable from the public directory (port 80)
• server-node port configurable
• a better way to handle the uploads and pix paths.
  I'm sure there will be more.

Currently all models are compiled in. Assuming all the models are stored on the server it should be a simple change to:

• retrieve a list of tables from the server to populate the top level menu (or just show a view on the table of tables)
• retrieve a specified table with its model as required.

Display collections as nested tables as per this example: http://bl.ocks.org/nautat/4085017.

Olivier, I tried setting this up in my local machine, is there a document where I can setup this and point to a database and build the UI.

Thanks for your help.

Krishna

The cause is simple: no file(s) at the given path(s). The wine flags work, the comics flags don't.

Suggestion: put all the country icon files in their own directory, say 'country'. Then they can be shared.

The error is
Module not found: Error: Can't resolve 'widgets/PageNotFound.js' in ...

I think the alias in config\webpack.config.dev.js is missing from config\webpack.config.prod.js. I tried fixing that, but then there are more.

Hi, I would like know if is there a simple way to use function like "group by" in evolutility-ui-react. for example I have a list of orders, I would like see the sum of orders by client.

Best regards.

Trying to work backwards off of your template models to expand upon them. Looking at Winetasting.js and specifically the wine_id field:

{ id: 'wine_id', entity: 'winecellar', column: 'wine_id', type: 'lov', label: 'Wine', inMany: true, width: 62, required: true },

When I attempt to add a new winetasting record or edit an existing, the LOV drop down list does not populate with available Wines. Is this field type intended to work as such? Attempting to rejoin the normalized structure that is created through the use of the LOV field type is tricky.

Running into an issue working with the React-UI and Node-Server backed on the same localhost for seemingly "non-simple" requests meaning all of the base GET API calls to the backend work fine, but trying to use the edit views for PUT API calls are getting interrupted. The React-UI will throw a Network Error - and digging into the developer console its looking like a CORS-related issue.

http://localhost:2000/api/V1/winecellar/5: Response for preflight is invalid (redirect)

I'm curious if anyone else has encountered this issue while trying to stand up the base apps.

Has anyone attempted to Dockerize this code base? When I go to run the app via docker I get the following error and just trying to troubleshoot where I've gone wrong as I've mirrored the same steps with a normal "local" install without any issues.

ERROR in ./src/components/views/many/Cards.js
Module not found: Error: Cannot resolve 'file' or 'directory' ../One/Card in /evolutility-ui-react/src/components/views/many
resolve file
/evolutility-ui-react/src/components/views/One/Card doesn't exist
/evolutility-ui-react/src/components/views/One/Card.webpack.js doesn't exist
/evolutility-ui-react/src/components/views/One/Card.web.js doesn't exist
/evolutility-ui-react/src/components/views/One/Card.js doesn't exist
/evolutility-ui-react/src/components/views/One/Card.json doesn't exist
resolve directory
/evolutility-ui-react/src/components/views/One/Card doesn't exist (directory default file)
/evolutility-ui-react/src/components/views/One/Card/package.json doesn't exist (directory description file)
[/evolutility-ui-react/src/components/views/One/Card]
[/evolutility-ui-react/src/components/views/One/Card.webpack.js]
[/evolutility-ui-react/src/components/views/One/Card.web.js]
[/evolutility-ui-react/src/components/views/One/Card.js]
[/evolutility-ui-react/src/components/views/One/Card.json]
@ ./src/components/views/many/Cards.js 25:12-34

Hello Oliver,

Really impressed by Evolutility so far, congrats!

I see that you have a Demo for the jquery version of the FrontEnd, do you plan to showcase one also for the React?

Looking forward to see it!

Many thanks,
Costin V.

It is breaking the optimized build (works fine in dev).

Hi,

Thanks for your great app. I'm able to add new model with less effort.

I have some questions

• Do you support search functionality?
  I can't find any example using search. I also find that the search flag is commented.
• Since I'm very new to react, can you give me a guidance to add search to a specific model?
  I have one model only so we can accept hard approach.

Thanks,
Van