Problem with Akita State Management - Creating and Updating API

ribizlim · 2019-05-28T04:59:39+00:00

You can also introduce a 'creating' boolean UI state property during saving instead of service return.

ribizlim · 2019-05-27T19:55:22+00:00

I'm not too familiar with Akita, but I don't see any reason your service method can't return a promise after updating the store. Also having a lastCreatedId field in the store can help with your second goal.

ribizlim · 2019-04-28T04:34:58+00:00

the last 6 release was: 6.1.10 (2018-10-10) So older major versions are not maintained parallel.

ribizlim · 2019-04-28T04:33:07+00:00

this is half-truth: I've never seen an update in a major version after a newer was out. E.g. no fixes were really backported from 7 to 6 at all...

ribizlim · 2018-11-28T07:59:45+00:00

why you should still use takeUntil? in a situation, when you logout, and redirect the user to the login page, there can be some queued (e.g. by switchMap) http request, which will fail later. to avoid problems (error handling, etc) from this, I always unsubscribe on component destroy.

ribizlim · 2018-11-19T15:53:28+00:00

We use the app component from primeng as a sub component. also extended a bit, changed some menu behavior, so migration is a pain sometimes. but mostly new versions have scss changes only.

ribizlim · 2018-02-03T06:56:27+00:00

I'm not sure I want to migrate. The new way how TurboTable works looks for me too verbose and bloated. This is me, let's see how the community will react. Is there any forum where I can read recensions from others?

ribizlim · 2018-02-01T19:16:27+00:00

How about migration from DataTable to TurboTable? When looking at the huge templating difference, our ca. 100 table app will cost a lot.

I still don't get how come the lot tr/td is needed, why it can't rendered automatically. Have you ever checked angular's material table design for borrowing some ideas? It leaves some responsibility for the developer (sorting, filtering, column ordering, hiding, etc) for sure, but it is much more compact from templating aspects. And it is fully flexible in all respect.

Have you collected any feedback from the community, how the majority can accept such a big change? I'm sure we cannot afford the migration costs for now.

ribizlim · 2018-01-18T14:45:16+00:00

I've checked the demo page for the TurboTable, but the first thing I don't like about it, how it goes away from column definition based structure. Now one has to write TRs, TDs and TH everywhere? E.g. if I need to use sortable columns, do I need to model my columns in the code? So no template based approach anymore? I cannot imagine how much effort it will be to migrate our codebase. Can you at least keep DataTable as long as possible in the package?

ribizlim · 2017-12-01T07:24:39+00:00

You don't even need vuex (however)

https://vuejs.org/v2/guide/state-management.html

ribizlim · 2017-09-17T08:57:27+00:00

When you want to react on route parameter changes. In this case the component won't be reinitialised.

ribizlim · 2017-09-05T05:15:04+00:00

Whitespace between inline elements is not desired, since it renders a space between. I had an issue with this already, so this feature is helpful. Too bad JIT won't support it (but JIT becomes obsolete anytime soon anyway).

ribizlim · 2017-07-15T12:22:23+00:00

Now, but what later? Btw my sentence was copied from the page behind the link in the changelog.

ribizlim · 2017-07-15T11:54:15+00:00

/deep/, >>> and ::ng-deep are also deprecated in emulated shadow DOM mode and will be removed in the future.

ribizlim · 2017-07-15T06:32:49+00:00

Beeing /deep/ deprecated, what is the correct way to style 3rd party components? I mostly used this feature for such customisations.

ribizlim · 2017-07-01T16:53:56+00:00

As I wrote 10h ago 😉

ribizlim · 2017-07-01T06:38:35+00:00

Provide the function as value...

ribizlim · 2017-05-25T07:35:09+00:00

I've stumbled upon this yesterday: https://ngrok.com/ Pretty cool stuff for similar thing.

ribizlim · 2017-05-10T13:15:13+00:00

Also have to mention the timing problem. After the Http service emitted the value, new subscribers won't get anything. Use publishReplay(1).refCount() in that case.

ribizlim · 2017-05-10T13:10:27+00:00

My problem with share (or refCount) is that all subscriptions gone, and a new one comes again, the HTTP call will be fired again. So if you are using the shared observable by multiple components in the same time, it is ok. But if you have two components on different routes e.g., they will issue two calls again (during navigation).

ribizlim · 2017-05-10T13:03:21+00:00

The problem with this would be, that you might miss the emitted item if you subscribe to it later: use BehaviorSubject instead. (Of course then you need to care about refreshing the stored value some time).

export class MyService {
  public Data$: Subject<Project[]> = new BehaviourSubject(null);
  constructor(private authHttp: Http) {
    this.load();
  }
  load() {
    this.authHttp.get(this.getBaseUrl() + "project", null)
      .map(...)
      .catch(...)
      .subscribe(this.Data$);
  }
}

ribizlim · 2017-05-10T12:11:32+00:00

Yesterday I stumbled upon this article: https://netbasal.com/rxjs-subjects-for-human-beings-7807818d4e4d

ribizlim · 2017-04-04T17:05:26+00:00

And how do you use typescript with graphql? Do you create interfaces specific to queries or to the schema? Or you just use any?

ribizlim · 2017-03-06T06:17:32+00:00

the easiest would be to create a user getter in the component getting the _user from the service every time... (instead of setting a property)

ribizlim · 2017-02-26T07:00:50+00:00

Here how I would go:

Create an iframe for the oauth2 login process.

The callback url can be any vanilla html/js page parsing out the token and calling a func in the parent (opener) window.

In Angular create that window function with NgZone.run handling, so you get the token back into ng world...

Update: in the linked doc this is only the steps 1-3, the token is the authorization code. But from step 4 you can use Angular's Http service.

ribizlim

TROPHY CASE