James Hou

Two decisions that led me to the below conclusions: 1) This is a developer first library - so creating more confusing APIs (input/output variables) but friendlier admin usage is not...

A couple more considerations came out of office hours: - Extra logic to consider for compound name fields. - Extra security check for parent relationship fields if `Lookup__r.Parent_Field__c` notation is...

Leaving some thoughts for now: ```js set editableFields(value = '') { this._isAllInlineEdit = value === INLINE_EDIT_KEY; this._editableFields = createFlattenedSetFromDelimitedString(value, ','); } ... // For future enhancements @wire(getObjectInfo, { objectApiName: '$_objectApiName'...

You’ll need to give the full soql string for debugging, it might have to do with how it splits and expectations of where keywords are. You’ve confirmed it runs in...

High level, this is not on the roadmap because of modal-ception. That is not something I'm willing to tackle right now (the impact of introducing that). For now, keeping this...

Fair approach, but I'm not really willing to take on such investment to support admin (apologies here) workflows. With a developer, they can take my output variables (selected rows) and...

Hey @solo-1234 the placement of the logic separate to `reference` only datatypes is not ideal. However, I see where you applied the potential fix. I have an idea that I...

I don’t agree nullish coalescing is the right blanket approach. The ethos of this library is to “pass through” whatever the platform provides and I only want to sparingly interject....

Update on this - my bandwidth is not looking so good in Q3 so will revisit in Q4

Added to [limitations](https://github.com/tsalb/lwc-utils/wiki/soqlDatatable:-Limitations#links-to-lookup-fields-on-parent-record-names-dont-work) wiki. No ETA on fix