forest-express-mongoose icon indicating copy to clipboard operation
forest-express-mongoose copied to clipboard

🌱 ExpressJS/Mongoose agent for Forest Admin to integrate directly to your existing ExpressJS/Mongoose backend application.

Results 73 forest-express-mongoose issues
Sort by recently updated
recently updated
newest added

[//]: # (dependabot-start) ⚠️ **Dependabot is rebasing this PR** ⚠️ If you make any changes to it yourself then they will take precedence over the rebase. --- [//]: # (dependabot-end)...

dependencies

## Pull Request checklist: - [ ] Write an explicit title for the Pull Request, following [Conventional Commits specification](https://www.conventionalcommits.org) - [ ] Create automatic tests - [ ] Test manually...

[//]: # (dependabot-start) ⚠️ **Dependabot is rebasing this PR** ⚠️ If you make any changes to it yourself then they will take precedence over the rebase. --- [//]: # (dependabot-end)...

dependencies

[//]: # (dependabot-start) ⚠️ **Dependabot is rebasing this PR** ⚠️ If you make any changes to it yourself then they will take precedence over the rebase. --- [//]: # (dependabot-end)...

dependencies

## Pull Request checklist: - [ ] Write an explicit title for the Pull Request - [ ] Write changes made in the CHANGELOG.md - [ ] Test manually the...

## Expected behavior I have a collection with several array fields: ``` const schema = Mongoose.Schema({ _id: { … }, … phones: [{ type: String }], websites: [{ type: String...

## Expected behavior I have couple models that I am experiencing this weird behaviour for: 'stashes', 'filters' and 'plans' however models called 'meals' or 'steps' work fine. My model id...

## Expected behavior Clicking a smart relationship shows data in the right hand pane. ## Actual behavior Clicking a smart relationship instead shows "No xxx. There are no xxx yet"....

Schema placed alongside node_modules, which is not desired behavior when using **npm 7 workspaces** Would be nice to have custom option or env variable to specify desired location of the...

## Expected behavior In our case, we use Unix (Epoch) time stored as an Int64 on MongoDB for all our Date/Time fields like created_on, updated_on, etc. We expect these fields...