Open stefjoosten opened 1 year ago
@stefjoosten, could you supply the interface.json file that was generated?
@stefjoosten, could you supply the interface.json file that was generated?
That is not needed. interface.json is not determining the UI elements.
@stefjoosten
Could be a browser cache thing. Open developer tools in chrome and then do a reload of the page with option disable cache marked. You find that option in the network tab of the developer tools.
I have tested this and I am sufficiently convinced (99%) that this is a browser cache thing.
If I make one information system that runs for years, like RAP, this is not an issue. However, if I am prototyping and making several updates to my system per day, things are different. In that case, this bug yields confusion and may cause the user to make unnecessary changes and spend time that could have been prevented.
So it still is a bug in the eyes of the user. What is the fix? Would that be to define a disabled cache in the browser as a requirement for the prototyping environment?
Hi @stefjoosten, I'm optimistic that this would not be an issue anymore with the new frontend framework we're building now. So I propose not spending time on fixing this particular issue for the current front end.
What happened
I wrote an interface
This is what came out:
What I expected
I expected no trash bin in front of "Ambulance" because the corresponding CRUd specifies a delete restriction.
Version of Ampersand that was used
I built this application FROM ampersandtarski/prototype-framework:v1.16.0 I compiled with Ampersand vs. 4.7.1