Chris D. Macrae

Potential problems/questions: - What do you do with the user-defined `objectId`? - Does it remain as the `objectId`? - This introduces the opportunity for duplicates. - Does the hash of...

Would this work better if instead of using objectID, we just add a configuration option to use _any_ field in an object record to calculate updates? That way we leave...

To add to this, if an `objectId` is found twice, algolia-indexing should throw an error to warn the user about this. We should never push duplicate objectIds to an index.

@hellt this tool still totally works -- however the project I intended to do the V1 update for got postponed, so the update has been stalled as well.

@curquiza this tool currently updates a single Algolia index with the least amount of operations. With the Algolia js sdk by itself, you update every record irregardless if they haven’t...

@tajchumber https://www.npmjs.com/package/parcel-plugin-asset-fourohfour Makes parcel throw a warning instead of an error for dependencies that can’t be resolved in HTML and CSS.

@bard do you mind sharing what you issue was?

@caymard It looks like the plugin can't resolve parcel's built-in logger. Are you sure parcel is available in your node modules and has a lib folder?

@TomMalow @magesoe As an alternative to the solution above, simply allowing the Xrm namespace to be renamed would also work, but I feel like this would feel less ergonomic. Again,...

Given that half of the files are static, my gut tells me the right approach is to: - add a unique token to both generated and static type declarations at...