In admin UI virtuals can't access field values not included in `defaultColumns`
See original GitHub issueIf you want to include a virtual to your defaultColumns
the fields it accesses must be included in defaultColumns
as well.
E.g.:
//not working:
Foo.schema.virtual( 'foo' ).get( function(){
return this.baz;
} );
Foo.defaultColumns = "name, foo";
//works:
Foo.schema.virtual( 'foo' ).get( function(){
return this.baz;
} );
Foo.defaultColumns = "name, baz, foo";
I assume some filtering of the document happens for speed reasons, which makes sense, but is there some way we can force the document to have specific fields inside our virtual getters?
Issue Analytics
- State:
- Created 9 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Configure the list layout - Product Documentation | ServiceNow
You can configure a list to choose which columns appear in a list, create list views, and create fields on the table.
Read more >Create a table and add fields - Microsoft Support
Learn how to create tables in Access and add fields to those tables.
Read more >Restrict access with column-level access control | BigQuery
Yes. You cannot copy columns if you don't have access to them. The following operations verify column-level permissions.
Read more >Firepower Management Center Configuration Guide ... - Cisco
When you configure user accounts, you enable web interface access and ... and Group Member URL Attribute fields with default values for the ......
Read more >The database abstraction layer - Web2py
where DEFAULT is a special value used to allow the value None for a parameter. Not all of them are relevant for every...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
closing as elemental UI merge makes this irrelevant.
+1 this bug is still present in 0.3.19