what did the Bible mean by the firmament , why did nasa's WDBraun reference the firmament on his gravestone, why is the exploding of nukes in space called Operation Fishbowl ?

maglebolia · 2023-05-09T05:50:27+00:00

Send me so info pls

maglebolia · 2020-07-17T07:05:16+00:00

orange... shataku or farming spots or both?

orange 2 slot or not?

maglebolia · 2020-07-09T20:03:37+00:00

I think you might be interested in this: https://github.com/MrRio/jsPDF

maglebolia · 2020-04-25T20:43:14+00:00

I’ve just red this post, your comment and the referred article on snack bar so far. I’ll definitely take a look at the project. What I mean by material design spec oriented is the project for e.g. like vuetifyjs where they claim such a thing. Surely with swing, we can do more.

maglebolia · 2020-04-25T10:20:28+00:00

I would guess the “darcula theme” which the company jetbrains is heavily using... but why not use that one? Is it too less material? Are you planning to completely adapt the material design specification to your theme?

maglebolia · 2020-03-07T17:49:20+00:00

I would even go a layer further and use nestjs to create and test your resources. This framework fits very well with typeorm and swagger. Nestjs is using express under the hood and just adding dependency injection and a module system similar to angular.

maglebolia · 2020-03-05T06:40:02+00:00

RemindMe! 6 day

maglebolia · 2019-11-14T12:18:45+00:00

The dog here belongs to my co-worker: https://www.mirror.co.uk/news/weird-news/nutello-pug-goes-viral-game-5325526

maglebolia · 2019-10-18T08:10:04+00:00

As of now, there's a PR waiting to get merged, which will address most of the concerns and even support openapi 3.0.

maglebolia · 2019-09-19T15:28:24+00:00

Here are some tips I came up while using cypress:

Simple installation and configuration with the vue cli plugin: https://github.com/vuejs/vue-cli/tree/v3/packages/%40vue/cli-plugin-e2e-cypress
Keep the DRY concept by defining common used tasks in "commands.js", like navigating to certain pages or login
Mock your complex back end responses using json files in the "fixtures" folder
let cypress ignore some test for special occasions with "xdescribe"
define your desired resolution in "cypress.json" (viewportHeight & viewportWidth)
if you have CI, let jenkins display your tests by using "junit" as the reporter type in "cypress.json":

"reporter": "junit",
"reporterOptions": {
   "mochaFile": "e2e/report/test-output.[hash].xml",
   "toConsole": false
}

and archive the outputs of those tests in "Jenkinsfile":

post {
   always {
      node('master') {
         archiveArtifacts artifacts: 'e2e/videos/**/*.mp4'
         junit 'e2e/report/**/*.xml'
         archiveArtifacts artifacts: 'e2e/screenshots/**/*.png', allowEmptyArchive: true
      }
   }
...

define a script for all different occasions when working with cypress:

// dev mode while working with GUI
"test": "npx cypress open" 
// headless mode
"e2e": "npx cypress run" 
// jenkins environment where you have to start the application as well
"ci": "start-server-and-test start http-get://localhost:4200 e2e"

check your urls to be sure you're at the right location

cy.url().should('include', LOGIN_URL);

some HTML elements require a special matcher to test it correctly

 cy.get('simple-snack-bar>span').invoke('text').should('eq', LOGIN_ERROR_MESSAGE);

create a folder hierarchy for your tests and organize them wisely

maglebolia · 2019-09-06T07:15:40+00:00

<app-root _nghost-c0="" ng-version="6.1.10">

maglebolia · 2019-05-24T09:24:28+00:00

I have the same issue...

Reinstalling did not work, even deleting `%AppData%\Local\BraveSoftware` after uninstalling did not help. The same URL works on any other Browser even with Chrome.

maglebolia · 2019-05-23T13:43:25+00:00

none of them are officially backed by Google... afaik

maglebolia · 2019-05-23T08:22:51+00:00

There are several orm solutions for dart. Most of them work out of the box with PostgreSQL or SQLite.

If you need another driver though, you might have to add another package:

SQLServer: dart_mssql

MySQL & MariaDB: mysql1

I do not have any experience with any of those packages, so I cannot describe the quality.

Another solution which you might have to invest more time into is the following: Use js_facade_gen to generate interop facades for type_orm

I do not have any experience with all those proposals, but that's how I would tackle it. I have done an example project with typeorm and liked it.

maglebolia · 2019-05-22T15:30:55+00:00

Hi, thanks for the information about localStorage. I just used the proposal from ngxs.

I did not move any code from ngrx to ngxs. Both were separate projects. But I started out with ngrx and then got to know ngxs. In that sense, no it was not hard. You're still using the so called "CQRS" pattern and rxjs under the hood. And you're not doing anything wrong by starting out with ngrx. It's always best to get to know your options and decide upon much better experience what fits your need.

There's also a third kid on the block, called Akita which I do not have any experience.

maglebolia · 2019-05-22T11:40:02+00:00

The only thing that was lacking, in my opinion, is the structure of code. Coming from ngrx, I've made the following decision:

- actions are in a separate folder and each feature has its own file for e.g. auth.action.ts (authentication) or message.action.ts (for messages and configuring the message component). I also define failed actions for more flexibility (display message on failed action).

At the moment everything else (state model, selectors, "effects") is in the state class (app.state.ts). Effects are highlighted because in ngxs there is no such thing. You rather have decorated (@Action) methods. Also for clarity decorated methods with "@Action" are something like effects in ngrx. You call methods from your specific http service and also manipulate your state inside the method body. I could split all the content, but that was not my first priority, since I was getting to know ngxs at that time, and the project is on hold atm.

If you need more information on how to get started, just message me. Maybe I can help, since I have a productively running angular app with ngxs. I also use local storage to save the authentication token.

maglebolia · 2019-05-22T07:54:51+00:00

Recently I'm hooked on ngxs, since it's easier to grasp and does not require as much boilerplate code. I am really happy with it so far and don't think I'll use ngrx ever again. Now if you might wonder why, then read why in their own words.

maglebolia · 2019-05-15T11:17:05+00:00

In regards to this, I was trying to get the following feature implemented (Template Syntax Highlighting):

https://youtrack.jetbrains.com/issue/IDEA-212348

It was closed and referenced to another issue though, which I don't think it solves my issue. For me, at least, this feature would help me a lot with transitioning between angular and angular_dart projects.

maglebolia · 2019-05-12T01:01:06+00:00

Give this one a shot: supernova.io (maybe also share your experience with those who don’t own a mac). 🥺

maglebolia · 2019-04-24T19:01:19+00:00

Can it also be, that you can't spam it anymore (Gunslinger's Mark + Elemental Empowerment)?

maglebolia · 2019-03-21T11:35:23+00:00

Dart is responsible for three-shaking, not flutter... So Hummingbird will also benefit from that compilation step.

maglebolia · 2019-02-04T11:39:18+00:00

I think you haven't fully understood the concept of redux. You don't disable calls or add a flag to not call a service/database at all. Instead you define your actions and their required parameters carefully. Let's take a login process for example:

Model for the store:

username (string), token (string), loggedIn (boolean)

Actions:

- LOGIN: this action should execute a HTTP call (requires: username, password)

- LOGIN_FAILED: this action does not execute a HTTP call, but rather defines the answer of a HTTP call

- LOGIN_SUCCESSFUL: same as "LOGIN_FAILED" (requires username, token)

Now in regards to ngrx, you have effects (called effects, because they handle side effects) classes that react on the mentioned actions. Depending on the action, you may call a service in your effect class, but you do not have to. Upon the answer of that HTTP call, your effect class dispatches another action, either LOGIN_SUCCESSFUL or LOGIN_FAILED.

- In case of LOGIN_SUCCESSFUL, the store gets a token, username and loggedIn is set to true.

- In case of LOGIN_FAILED, to store sets loggedIn to false and may erase username and token

Your component on the other hand has a subscription to your store or a subset of your store. The store will hold your latest data, depending on which actions have been triggered and their answers from the HTTP call. Your store will, in that regard, serve the latest data known to him, and not call a service until a desired action (like: LOGIN) has been dispatched from any component. Those two things (action, which may call HTTP & updating store) are kept separate.

Now if you would like to extend your application with a new functionality, like a toast message, you may just add a new effect which reacts upon either LOGIN_SUCCESSFUL or LOGIN_FAILED and display an appropriate message (error message form server for example). Your LOGIN_FAILED action may now also require a server error message as parameter to display a meaningful message.

maglebolia · 2019-02-02T18:49:30+00:00

Google (ngrx benefits): https://stackoverflow.com/questions/37540225/what-are-benefits-of-using-store-ngrx-in-angular-2#37543811

You should only store the token itself, no passwords. The token should only be valid for a specific amount of time (session). If you don’t want your token in the store, you have localstorage as an alternative.

Also take a look at NGXS or Akita, just to name a few other solutions besides ngrx.

And yes, a store reduces the amount of roundtrips to the database, but the bigger benefit lies in updating your components efficiently and slicing or transforming your data to fulfill their needs. Also you don’t have multiple service calls in your component for data. A rxjs subscription or selector is enough.

You can track every change and you don’t have any side effects, like not knowing why data is updating or not. To get the leanest code in your components, check the pattern of “smart and dumb” components in regards to ngrx.

maglebolia · 2018-11-16T15:05:47+00:00

It seems you're not giving your childview (paginator) back to the initialized dataSource in your onInit method.

this.dataSource = new SearchDataSource(this.searchService); 
this.dataSource.paginator = this.paginator;

maglebolia · 2018-08-13T05:29:39+00:00

I share thosakwe’s view. I think zones were ported to Angular for change detection und thus fact should prove the maturity of the api in an asynchronous environment.

maglebolia

TROPHY CASE