DRCIT/snipe-it
1
0
Fork 0
mirror of https://github.com/snipe/snipe-it.git synced 2025-02-02 08:21:09 -08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Fixes javascript error when custom fields exist but do not belong to any fieldsets or models

Browse source
This commit is contained in:
snipe 2017-07-26 17:06:58 -07:00
parent ee7348d0d5
commit ccb7556281
1 changed files with 11 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
app/Presenters/AssetPresenter.php
View file

@ -184,7 +184,17 @@ class AssetPresenter extends Presenter
], ],
]; ];
$fields = CustomField::all(); // This looks complicated, but we have to confirm that the custom fields exist in custom fieldsets
// *and* those fieldsets are associated with models, otherwise we'll trigger
// javascript errors on the bootstrap tables side of things, since we're asking for properties
// on fields that will never be passed through the REST API since they're not associated with
// models. We only pass the fieldsets that pertain to each asset (via their model) so that we
// don't junk up the REST API with tons of custom fields that don't apply
$fields = CustomField::whereHas('fieldset', function ($query) {
$query->whereHas('models');
})->get();
foreach ($fields as $field) { foreach ($fields as $field) {
$layout[] = [ $layout[] = [
"field" => 'custom_fields.'.$field->convertUnicodeDbSlug(), "field" => 'custom_fields.'.$field->convertUnicodeDbSlug(),