Tremendus Apps

Request Object not available from response

1

Hi, great library, my favorite Ajax lib actually ... I see from the docs and the source that there is no obvious way to get to the request object from...

Create 'reactive' representation of state of datat in Parse.Object eg for use in libraries like React, VueJS, etc

2

**Is your feature request related to a problem? Please describe.** A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Front end libraries like...

TypeError when bundling latest Parse JS SDK using VITE (the vue bundler)

19

### New Issue Checklist - [x] I am not disclosing a [vulnerability](https://github.com/parse-community/parse-server/blob/master/SECURITY.md). - [x] I am not just asking a [question](https://github.com/parse-community/.github/blob/master/SUPPORT.md). - [x] I have searched through [existing issues](https://github.com/parse-community/Parse-SDK-JS/issues?q=is%3Aissue). -...

ParseObject#fetch should expose the same control over returned fields/pointers that Parse.Query does

1

**Is your feature request related to a problem? Please describe.** Currently, Parse.Query offers several methods to select/exclude fields and include related objects - `#select`, `include`, `exclude` However, `Parse.Object#fetch` does not...

Consider dynamic parent/child matching fn()

1

https://github.com/DenQ/list-to-tree/blob/06f51966783687eff82645b96de136a6a8bd2853/dist/list-to-tree.js#L39 I have a need to generate a tree from a collection (array of objects). But my paths are nested - eg: ``` { id: 100, field: 'val', // ......

Updating a component moves the component outside of Root svelte component

1

### Describe the bug The seems to be a reproducible bug somewhere between Vite and Svelte that causes a component being updated in the editor to become moved outside of...

```javascript const arrayOne = [ 1, 2, 3, 4, 5 ] const arrayTwo = [ 4, 5, 6, 7 ] const intersection = arrayOne.filter(item => arrayTwo.includes(item)) ```

### Describe the bug The seems to be a reproducible bug somewhere in dev tools that causes a component being updated in the editor to become moved outside of the...