Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add event listener evolution to new standard supporting options object as third argument #2030

Open
wants to merge 415 commits into
base: master
Choose a base branch
from

Conversation

marchant
Copy link
Member

No description provided.

- first working version of requiring es files with import/export
- slight improvement in xhr use for loading
- fix collections set require
- Fix isSearchable default
- add missing descriptor
…o it can be shared shared between setting expression and syntax.
…a if it's not included by server and they are known client side, before processing as usual
-  move failsafe against fetching object properties of created objects from DataTrigger to DataService, allowing more finesse for fetching properties of newly created objects that can based on their current values set, still preventing cases where a typical primary key would be involved in the fetch
-  makes isObjectCreated more robust to just using this.createdDataObjects as some promises now involved in fetching object, properties because it's not done at the DataTrigger level, can fire after a saveChanges() may have wiped this.createdDataObjects
- improve/fix bug dealing with mapping added/removed values
- add method to create a criteria that supports compound primaryKeys
- add ability for foreign value converter to work for properties, including if fetch depend on the values of other properties of the same object. Add readExpression to query in that case so RawDataService involved has a cue
…or, with the ability to call .next(aType) to move through the tree with more finesse. Because syntax is built by the parser generated by Peg, we don't have a type where we could get the iterator from.
that impacts every listeners dispatched after
handleOrganizedContentRangeChange because
it modifies the passed argument.
…EventListener. Performance comparison with master are needed.
…do rather than doing upfront before we know wether there are listeners or not.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant