johneke/acre

admin-page, crud, and rest api generator for node js

acre's Issues

Cyclic Refs are broken

Nested refs are supported, but there is an infinite loop when there is a Cyclic ref.

Use mongoose.model.new() to init default instances

This helps prefill acre admin pages with data that has been defaulted on the server side

Not possible to set new field on legacy document without specifying a default in the schema

1. Go on the server server and add a new field to the schema of a pre existing document. Do not specify a default
2. Restart the server
3. Go to acre admin and edit a document that existed before you added the new field to the model

Result:
New field is not available to be edited

Expected:
New field should be available to edit/set

Cancelling update to a ref field still sets the ref

1. Open acre/admin
2. Click on one document
3. Look for a ref inside that document and click 'Edit'
4. In the dialog that pops up, click cancel

Result:
The same ref which is already there gets POSTed to the server again

Expected:
Nothing should happen

Cannot add multiple acre.pre middleware to the same route

Cannot add multiple acre.pre middleware to the same route

acre does not support enums

acre does not support enums

Restangular cannot send empty tex/plain POST with empty body

For fields that are permitted to be empty, Restangular cannot send an empty string if there is no data in POST body.

Result is that database object fields cannot be updated to an empty string

REST API should return error messages from mongoose regex validation

REST API should return error messages from mongoose regex validation

Use template-literal instead of EJS

Template Literal is fastest, smallest and simplest template engine, because it use JS's literal template feature.

It's 55 times faster than EJS, and it also use less CPU and RAM ressources, so it may be a good idea to use it instead of EJS 😀

acre nested refs does not support any data having an apostrophe

Steps to reproduce, need 2 models where one is a ref on the other

1. Go to model/create page and create an object for the model with no refs, and save
2. Go to model/create page for second object which has a ref to the first

Result:
No form is visible for create (stack trace in console)

Expected:
Should see create form for second object

Need solution to ref problem

Proposition:

Drop support for auto populating refs on GET. For GET, send ref ids, and let clients request refs on demand

Full support for refs in admin portal for edit, and and

Admin portal throws exception when viewing old object of updated model

1. Use admin portal to create new model
2. Add new field to schema
3. Reload app
4. View same object
5. Throws exception