Meteor-Community-Packages / Meteor-Community-Packages/meteor-tabular
Add publishAllFields option
- Dominant language
- JavaScript
- Stars
- 360
- Forks
- 132
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I understand that there is the extraFileds: option do define other fields.
But it would be great to have another option to simply tell server-side to publish all (other) fields by default which are not defined in data columns. Especially when having a lot of fields defined in SimpleSchema, Collection2 with quick forms causes a lot of manual work to define fields.
If there is a hint on how to simplify the manual work, I would appreciate this feedback.
Thanks.

Disabling some columns should still allow to edit other fields. But the publishing reduces the object for fields defined (see attached image of GreatAlbums example)
```
TabularTables.AlbumsList = new Tabular.Table({
name: "Great Albums List",
collection: Albums,
columns: [
{data: "artNr", title: "Art.Nr", class: "col-md-1"},
{data: "artistName", title: "Artist", class: "col-md-3"},
{data: "albumTitle", title: "Title", class: "col-md-4"},
{data: "inStock", title: "In stock", class: "col-md-1"},
{data: "backOrdersPossible", title: "Backorders Possible", class: "col-md-1"},
//{data: "price", title: "Price", class: "col-md-1"},
{
tmpl: Meteor.isClient && Template.AlbumActionBtns, class: "col-md-1"
}
]
});
```
Contributor guide
Research direction
No file or test is named. Start by tracing the Tabular.Table configuration and its server-side publication behavior, using the AlbumsList example as the reproduction case; done means an option can publish fields outside the listed data columns while omitted columns remain disabled in the table.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100