Tweek's javascript client fetch function should have a simpler option when there's no need to override context

[Gabrn]

The api for fetching configurations forces the client to pass a configuration object with a nested context object and another nested object per entity type even if there's no need to override the context and there's a need for only one entity. It is also a little weird for the client in general when the context is part of the options object.

Suggestion:

Create an overload utility function for passing only entity type and id:

await tweekClient.fetch("path/to/configuration", "user", "Yshay", options);

[Yshayy]

What about { user: “John”}, it’s more consistent with both js and Tweek rest style?

[Gabrn]

Ok, lets do that then.
I also think it's a good idea to separate the context object from the other options object.
I don't think people who use the js sdk think about how it looks like in rest.

So it should be:

1. client.fetch("config", {user: "John"}, options)
2. client.fetch("config", {user: {id: john, contextOverride: "bla"}}, options)

[Yshayy]

It’s not necessary override, it’s context properties

[Yshayy]

the semantics of context are important whether you use rest or other tweek client

[Yshayy]

Also the client support giving context in ctor.

[tal952]

Also the client support giving context in ctor.

Wow, you right!
So the context in fetch basically used only for context override?

[Yshayy]

Could be expansion, not just override.
I think the context shorthand syntax is useful and more concise.
If we use it, it should be implemented in ctor and Tweek-local-cache lib as well

[Gabrn]

Cool, so just so we’re clear which options do you think we should implement @Yshayy

[Yshayy]

I think adding Shorthand syntax support for context.
Support of string identifier instead of an object with id field (full object should be still supported)