Todd Baert

Changes in sequelize to avoid calling model function overrides break alias-inference logic

8

I believe https://github.com/sequelize/sequelize/commit/b253d8ed63c91bc2c7143f07806554b5a5ac67eb breaks the alias-inference logic in `sequelize-typescript`. I believe this is because this change breaks the proxy behavior that `sequelize-typescript` relies on. I have opened an issue with...

Is support for pagination and 'multi' create needed?

5

I'd love to create a PR to support pagination: https://docs.feathersjs.com/api/databases/common.html#pagination As well as to add support for 'multi' create: https://docs.feathersjs.com/api/services.html#create-data-params If I'm not missing anything, these need to be added....

With increased participation in the project it's become apparent that we need to efficiently and effectively manage access to repositories. We can use Github's teams OR `OWNERS_ALIASES`, combined with specific...

Adds document statuses explaining stability of various spec documents and sub-sections.

NX automatically adds `"type": "commonjs"` to package.json when using generators, which breaks imports with 16.8 changes

6

### Current Behavior New packages created with generators have `"type": "commonjs"` in their `package.json`, which in [email protected] prevents them from being imported by some projects (for example, a vanilla `create-react-app`...

[Static-context Paradigm] How to handle errors in `on context changed`

2

In static-context-paradigm (aka client paradigm), the provider [context-changed](https://openfeature.dev/specification/sections/providers#26-provider-context-reconciliation) handler runs to help reconcile the new global context with the provider's state (and in many cases the underlying SDK's state). This...

Spec styling and consistency issues

2

As mentioned [here](https://github.com/open-feature/spec/pull/182#discussion_r1192449336), there's some consistency issues with the non-normative parts of the spec. It would be great to get a thorough review of this. These proposed fixes are all...

Return value and `after` stage errors

18

As pointed out [here](https://github.com/open-feature/dotnet-sdk/pull/109), the spec doesn't dictate whether the `evaluated flag value`, or the `default value` should be returned in the case of an error in the AFTER stage...

* existing repo requirements and DCO section moved here from .github (will redirect them to here after merge) * added semantic versioning + breaking changes section * added platform support...

### Requirements #### Stateless providers Providers no longer maintain their own state: the state for each provider is maintained in the SDK automatically, and updated according to the success/failures of...