Add OverlappingMarkerSpiderfier package #1329

chancezeus · 2018-02-24T13:03:10Z

As mentioned in #1146 it would be nice to have support for the OverlappingMarkerSpiderfier. Since a lot of (if not most) people would also like to be able to combine the spiderfier with the cluster library I made some changes to the way the MarkerManager works. The change basically makes it possible for MarkerManagers to be nested which enables the spider and cluster plugins to be active at the same time (ordering should not matter) and forwarding the actual creation of markers onto the "parent" MarkerManager (this will be the MarkerManager instance associated with the AgmMap instance). I did not want to modify too much in the core packages, but I did extend the base MarkerManager constructor with an @Optional() @SkipSelf() _markerManager: MarkerManager. If interested I can add extra functionality to also have the "core" MarkerManager forward it's calls up the tree (until the "parent" is not defined anymore) and thus add the option to create for example an AgmMarkerGroup directive that clusters similar markers which can be disabled at once and/or other (more advanced) features...

sebholstein

Nice work!

I added some comments. We should also change the naming a bit:

Package name: @agm/marker-spiderfier
Folder name: marker-spiderfier

sebholstein · 2018-03-03T11:04:23Z

packages/spiderfier/directives/marker-spider.ts

+  /**
+   * Triggers when a marker is formatted, can be used to style the icon
+   */
+  @Output() format: EventEmitter<{ marker: Marker, status: string }> = new EventEmitter<{ marker: Marker, status: string }>();


Can we extract this as a type? So others can use this in their code.

sebholstein · 2018-03-03T11:04:37Z

packages/spiderfier/directives/marker-spider.ts

+  /**
+   * Triggers when markers are spiderfied (expanded)
+   */
+  @Output() spiderfy: EventEmitter<{ changedMarkers: Marker[], unchangedMarkers: Marker[] }> = new EventEmitter<{ changedMarkers: Marker[], unchangedMarkers: Marker[] }>();


same here for the type

sebholstein · 2018-03-03T11:06:29Z

packages/spiderfier/README.md

+
+-----
+
+this package levereges the [npm-overlapping-marker-spiderfier][npm-overlapping-marker-spiderfier] to add spiderfy


this -> This

sebholstein · 2018-03-03T11:09:58Z

packages/spiderfier/directives/marker-spider.ts

+ */
+@Directive({
+  selector: 'agm-marker-spider',
+  providers: [


as want to start implementing ChangeDetectionStrategy.OnPush for all component: can you add it here and test that it runs with OnPush?

The changeDetection attribute is only available for components, not directives. Please update the @agm/core package and I'll test if this gives any problems in my package

sebholstein · 2018-03-03T11:10:23Z

packages/spiderfier/directives/marker-spider.ts

+  /**
+   * Triggers when markers are unspiderfied (collapsed)
+   */
+  @Output() unspiderfy: EventEmitter<{ changedMarkers: Marker[], unchangedMarkers: Marker[] }> = new EventEmitter<{ changedMarkers: Marker[], unchangedMarkers: Marker[] }>();


same here for the type

sebholstein · 2018-03-03T11:21:04Z

packages/spiderfier/README.md

+@agm/js-marker-spider has a peer depedency on [npm-overlapping-marker-spiderfier][npm-overlapping-marker-spiderfier]
+
+```shell
+npm install npm-overlapping-marker-spiderfier @agm/js-marker-spider --save


We should use a version range here for npm-overlapping-marker-spiderfier that works with our package.

I actually made a full ts rewrite of the package that is 100% compatible but forgot to update the readme, I will update and include version info

sebholstein · 2018-03-03T11:21:11Z

packages/spiderfier/README.md

+```shell
+npm install npm-overlapping-marker-spiderfier @agm/js-marker-spider --save
+# or
+yarn add npm-overlapping-marker-spiderfier @agm/js-marker-spider


See previous comment

sebholstein · 2018-03-03T11:24:01Z

packages/spiderfier/services/managers/spider-manager.ts

+
+    const markerPromise = this._markerManager.getNativeMarker(marker);
+
+    this._markers.set(marker, markerPromise);


This happens in the _makerManager.addMarker already

True, but the _markerManager is a reference to the parent (notice the @SkipSelf) which means that the local _markers is not updated. By setting the _markers here too, it allows for the manager to keep a local reference to it's own markers which is used in removal/clear to only delete markers owned by the spiderfier, not by any parent (cluster/agm-map) managers)...

The update(s) to core (as explained in the intro) are to allow cascading of marker creation from "nested" marker managers up the chain (until the "core" marker manager belonging to the "agm-map" directive, that way it is possible to have a clustered-spiderfier (or any other nested (grouping) marker layer)...

sebholstein · 2018-03-03T11:24:23Z

packages/spiderfier/services/managers/spider-manager.ts

+      if (this._markers.has(marker)) {
+        spider.removeMarker(nativeMarker as any);
+
+        this._markers.delete(marker);


This happens in the _makerManager.addMarker already

See previous comment

sebholstein · 2018-03-03T11:25:49Z

packages/spiderfier/services/managers/spider-manager.ts

+  }
+
+  createEventObservable<T>(eventName: string, marker: AgmMarker): Observable<T> {
+    // Override the default "click" event with "spider_click"


Could it be a valid use case that the user want's a click event instead of a spider_click event?

The click event in the spiderfier is not very functional since it will also trigger when the "root" marker is clicked. Long story short: the click event might be usefull for only very few people and to (properly) support the info window, I have to replace the click event (otherwise the infowindow will also trigger when clicking the still collapsed markers)...

If you (or anyone) has a suggestion I'm all ears...

chancezeus · 2018-03-03T20:50:44Z

I pushed a commit with most of the changes, please comment on the few ones remaining with questions and I'll modify and commit accordingly...

chancezeus · 2018-03-12T09:13:51Z

@SebastianM the requested replacements of (?:../)+core to @agm/core result in the failing travis checks since travis does not know about the @agm/* packages when it runs. Unfortunately my experience with travis is limited but I guess some additional config (mapping @agm/* to the correct paths) is needed to make the test(s) run correctly again...

chancezeus · 2018-03-12T09:22:14Z

Example of nested cluster and spiderfier (this comes from my own (working) test component):

<agm-map [latitude]="51.673858" [longitude]="7.815982" [maxZoom]="16">
  <agm-marker-cluster [maxZoom]="14"
                      imagePath="https://raw.githubusercontent.com/googlemaps/v3-utility-library/master/markerclustererplus/images/m">
    <agm-marker-spider [keepSpiderfied]="true" (format)="testEvent('format', $event)"
                       (spiderfy)="testEvent('spiderfy', $event)" (unspiderfy)="testEvent('unspiderfy', $event)">
      <agm-marker [latitude]="51.673858" [longitude]="7.815982"
                  (markerClick)="testEvent('markerClick', $event)"></agm-marker>
      <agm-marker [latitude]="51.673858" [longitude]="7.815982"
                  (markerClick)="testEvent('markerClick', $event)"></agm-marker>
      <agm-marker [latitude]="51.673858" [longitude]="7.815982"
                  (markerClick)="testEvent('markerClick', $event)"></agm-marker>
      <agm-marker [latitude]="51.673858" [longitude]="7.815982"
                  (markerClick)="testEvent('markerClick', $event)"></agm-marker>
      <agm-marker [latitude]="51.67" [longitude]="7.8"
                  (markerClick)="testEvent('markerClick', $event)"></agm-marker>
    </agm-marker-spider>
  </agm-marker-cluster>
</agm-map>

@agm

- Replace google.maps types with corresponding @agm types

ChrisDevinePimss · 2018-03-23T07:43:48Z

@SebastianM any update on this?

felberto · 2018-04-20T13:18:59Z

@SebastianM are there any updates on this?

Murali1689 · 2018-05-04T08:47:15Z

@SebastianM Any updates on this?

Satheesh28 · 2018-07-06T12:16:59Z

<agm-marker-cluster [maxZoom]="14"
imagePath="https://raw.githubusercontent.com/googlemaps/v3-utility-library/master/markerclustererplus/images/m">
<agm-marker-spider [keepSpiderfied]="true" (format)="testEvent('format', $event)"

this not working for me please help me @chancezeus

lam3rr · 2018-07-27T08:43:58Z

@SebastianM are there any updates on this?

WheelyWonka · 2018-09-12T14:15:27Z

Hola ! Any update on this ? Thanks !

amorimdev · 2018-10-02T20:54:59Z

@SebastianM Any updates on this?

amorimdev · 2018-10-03T14:09:35Z

@chancezeus I have had to use this feature so I took the liberty to publish a package.

If anyone feel interested to, follow link of the package.
https://www.npmjs.com/package/agm-oms

ChrisDevinePimss · 2018-10-03T14:11:38Z

@chancezeus I have had to use this feature so I took the liberty to publish a package.

If anyone feel interested to, follow link of the package.
https://www.npmjs.com/package/agm-oms

You sir are my hero 4 the day!

drjaat · 2018-10-04T08:59:13Z

@chancezeus I have had to use this feature so I took the liberty to publish a package.

If anyone feel interested to, follow link of the package.
https://www.npmjs.com/package/agm-oms

error agm-marker-spider is not known element
and i have added this to app.module.ts in import also but no working

btimeteam · 2018-10-05T22:35:48Z

@drjaat you import agm-oms in same location where you imports @agm/core? And you export AgmMarkerSpiderModule? If you do not try export this module.

Smiter15 · 2018-10-08T09:12:17Z

@chancezeus I have had to use this feature so I took the liberty to publish a package.

If anyone feel interested to, follow link of the package.
https://www.npmjs.com/package/agm-oms

Does this play well with marker clusterer ? If so can you update the README with the syntax please

ChrisDevinePimss · 2018-10-08T10:48:33Z

@chancezeus I have had to use this feature so I took the liberty to publish a package.
If anyone feel interested to, follow link of the package.
https://www.npmjs.com/package/agm-oms

Does this play well with marker clusterer ? If so can you update the README with the syntax please

I tested it and found that it does

Smiter15 · 2018-10-08T11:11:12Z

@chancezeus I have had to use this feature so I took the liberty to publish a package.
If anyone feel interested to, follow link of the package.
https://www.npmjs.com/package/agm-oms

Does this play well with marker clusterer ? If so can you update the README with the syntax please

I tested it and found that it does

Thanks for the reply. When using it in my setup I have a clustered marker of 2 and when I click on it, it just flashes and doesn't separate. Here is my mark up:

<agm-map (mapReady)="mapReady($event)">
    <agm-marker-cluster imagePath="https://raw.githubusercontent.com/googlemaps/v3-utility-library/master/markerclustererplus/images/m">
        <agm-marker-spider>
            <agm-marker *ngFor="let marker of markers" [latitude]="marker.lat" [longitude]="marker.lang">
                <agm-snazzy-info-window [closeWhenOthersOpen]="true">
                    <ng-template>
                        <div class="row pop-over-content">
                            ...
                        </div>
                    </ng-template>
                </agm-snazzy-info-window>
            </agm-marker>
        </agm-marker-spider>
    </agm-marker-cluster>
</agm-map>

Is this correct ? I don't get any errors.
When I remove the agm-clusterer tag it works and spiderfies the 2 markers :/

ChrisDevinePimss · 2018-10-08T12:27:11Z

turn clustering off at a certain zoom point using [maxZoom]="10"

I changed your code to as below code below

<agm-map (mapReady)="mapReady($event)">
    <agm-marker-cluster [maxZoom]="10" imagePath="https://raw.githubusercontent.com/googlemaps/v3-utility-library/master/markerclustererplus/images/m">
        <agm-marker-spider>
            <agm-marker *ngFor="let marker of markers" [latitude]="marker.lat" [longitude]="marker.lang">
                <agm-snazzy-info-window [closeWhenOthersOpen]="true">
                    <ng-template>
                        <div class="row pop-over-content">
                            ...
                        </div>
                    </ng-template>
                </agm-snazzy-info-window>
            </agm-marker>
        </agm-marker-spider>
    </agm-marker-cluster>
</agm-map>

Smiter15 · 2018-10-08T13:05:23Z

turn clustering off at a certain zoom point using [maxZoom]="10"

I changed your code to as below code below

<agm-map (mapReady)="mapReady($event)">
    <agm-marker-cluster [maxZoom]="10" imagePath="https://raw.githubusercontent.com/googlemaps/v3-utility-library/master/markerclustererplus/images/m">
        <agm-marker-spider>
            <agm-marker *ngFor="let marker of markers" [latitude]="marker.lat" [longitude]="marker.lang">
                <agm-snazzy-info-window [closeWhenOthersOpen]="true">
                    <ng-template>
                        <div class="row pop-over-content">
                            ...
                        </div>
                    </ng-template>
                </agm-snazzy-info-window>
            </agm-marker>
        </agm-marker-spider>
    </agm-marker-cluster>
</agm-map>

Works a treat ! Thank you

AScheidt · 2018-10-29T14:27:06Z

This extension works great! Just one question: How do I use the [legColors] in <agm-marker-spider> correctly? I want to set the usual and highlighted properties of the legColors: LegColorOptions property to a certain color, but don't know how to achieve this.

AScheidt · 2018-10-29T15:54:32Z

@chancezeus I have had to use this feature so I took the liberty to publish a package.

If anyone feel interested to, follow link of the package.
https://www.npmjs.com/package/agm-oms

I'm getting the error:
Error: Uncaught (in promise): TypeError: _this._markerManager.deleteMarkers is not a function TypeError: _this._markerManager.deleteMarkers is not a function at spider-manager.js:72

I think it's a typo isn't it? Because spider-manager.js tries to call _this._markerManager.deleteMarkerS when there is only a Method calles deleteMarker()

rgails · 2019-01-25T17:31:14Z

@chancezeus I have had to use this feature so I took the liberty to publish a package.
If anyone feel interested to, follow link of the package.
https://www.npmjs.com/package/agm-oms

I'm getting the error:
Error: Uncaught (in promise): TypeError: _this._markerManager.deleteMarkers is not a function TypeError: _this._markerManager.deleteMarkers is not a function at spider-manager.js:72

I think it's a typo isn't it? Because spider-manager.js tries to call _this._markerManager.deleteMarkerS when there is only a Method calles deleteMarker()

Someone fixed it in a different version of the package: https://www.npmjs.com/package/agm-spiderfeir

azurenote · 2019-02-08T05:17:00Z

This extension saved my days. Thank you for your great work. Hope this fully merged to main branch.

stale · 2019-05-09T06:06:27Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

henryyue2010 · 2019-08-09T23:18:30Z

I met problems when trying to use agm-oms with js-marker-clusterer. Hopfully, the package of marker spiderfier can be fully supported in agm asap. Thank you very much.

stale · 2019-11-08T00:09:07Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

CrackerakiUA · 2019-11-18T20:44:16Z

when this will be completed? :)

ghost · 2019-11-19T16:30:27Z

Whenever someone adopts this PR and makes the necessary changes. I won't be doing it anytime soon, since there are more pressing issues.

anotherboz · 2019-11-26T15:44:51Z

I resolved conflicts, rebuild the angular-spiderfier plugin and published the new package under https://www.npmjs.com/package/agm-spiderfier

Now, I don't know if it's better to keep this package distinct or merge it in agm.

CrackerakiUA · 2019-12-02T15:34:14Z

404 Not Found: @agm/js-marker-spider@1.0.5 @anotherboz latest also not working. And if I install agm/js-marker-spider I see error from code: ERROR in src/app/common/Map/map/map.module.ts(10,39): error TS2307: Cannot find module 'agm/js-marker-spider'.

albuquerquefabio · 2020-02-20T00:04:12Z

I resolved conflicts, rebuild the angular-spiderfier plugin and published the new package under https://www.npmjs.com/package/agm-spiderfier

Now, I don't know if it's better to keep this package distinct or merge it in agm.

It work perfect!
But, your new version 1.0.6 is the correct one.

CrackerakiUA · 2020-05-07T22:09:58Z

I resolved conflicts, rebuild the angular-spiderfier plugin and published the new package under https://www.npmjs.com/package/agm-spiderfier
Now, I don't know if it's better to keep this package distinct or merge it in agm.

It work perfect!
But, your new version 1.0.6 is the correct one.

well, good point, it works under https://www.npmjs.com/package/agm-spiderfier1 with latest agm/core

shahabas-cp-14 · 2020-05-08T18:28:25Z

I resolved conflicts, rebuild the angular-spiderfier plugin and published the new package under https://www.npmjs.com/package/agm-spiderfier
Now, I don't know if it's better to keep this package distinct or merge it in agm.

It work perfect!
But, your new version 1.0.6 is the correct one.

well, good point, it works under https://www.npmjs.com/package/agm-spiderfier1 with latest agm/core

but when I try to take the production build, I am getting the error : Module not found: Error: Can't resolve 'agm-spiderfier'

albuquerquefabio · 2020-05-20T08:00:41Z

I resolved conflicts, rebuild the angular-spiderfier plugin and published the new package under https://www.npmjs.com/package/agm-spiderfier
Now, I don't know if it's better to keep this package distinct or merge it in agm.

It work perfect!
But, your new version 1.0.6 is the correct one.

well, good point, it works under https://www.npmjs.com/package/agm-spiderfier1 with latest agm/core

but when I try to take the production build, I am getting the error : Module not found: Error: Can't resolve 'agm-spiderfier'

I had the same problem and to solve it follow this:

Install as dev Dependencies

npm i -D @type/jest@25.2.1

Install as Dependencies

npm i --save @agm/core@1.1.0 agm-spiderfier@1.0.0 agm-spiderfier1@1.0.6
npm i --save ts-overlapping-marker-spiderfier@1.0.2 agm-oms

At your tsconfig.app.json

{
  "extends": "./tsconfig.json",
  "compilerOptions": {
    "outDir": "./out-tsc/app",
    // Add  types jest
    "types": ["jest"]
  },
  "include": [
    "src/**/*.ts",
    // Add agm-spiderfier to be compiled
    "./node_modules/agm-spiderfier/**/*.ts"
  ],
  "exclude": ["src/test.ts", "src/**/*.spec.ts"]
}

ghost · 2020-07-03T13:08:15Z

replaced by #1771

crac7 · 2021-04-28T21:05:44Z

not work !

I resolved conflicts, rebuild the angular-spiderfier plugin and published the new package under https://www.npmjs.com/package/agm-spiderfier
Now, I don't know if it's better to keep this package distinct or merge it in agm.

It work perfect!
But, your new version 1.0.6 is the correct one.

well, good point, it works under https://www.npmjs.com/package/agm-spiderfier1 with latest agm/core

but when I try to take the production build, I am getting the error : Module not found: Error: Can't resolve 'agm-spiderfier'

I had the same problem and to solve it follow this:

Install as dev Dependencies

npm i -D @type/jest@25.2.1

Install as Dependencies

npm i --save @agm/core@1.1.0 agm-spiderfier@1.0.0 agm-spiderfier1@1.0.6
npm i --save ts-overlapping-marker-spiderfier@1.0.2 agm-oms

At your tsconfig.app.json
{
  "extends": "./tsconfig.json",
  "compilerOptions": {
    "outDir": "./out-tsc/app",
    // Add  types jest
    "types": ["jest"]
  },
  "include": [
    "src/**/*.ts",
    // Add agm-spiderfier to be compiled
    "./node_modules/agm-spiderfier/**/*.ts"
  ],
  "exclude": ["src/test.ts", "src/**/*.spec.ts"]
}

ffuf-ralphnival · 2022-05-03T00:01:52Z

turn clustering off at a certain zoom point using [maxZoom]="10"
I changed your code to as below code below

<agm-map (mapReady)="mapReady($event)">
    <agm-marker-cluster [maxZoom]="10" imagePath="https://raw.githubusercontent.com/googlemaps/v3-utility-library/master/markerclustererplus/images/m">
        <agm-marker-spider>
            <agm-marker *ngFor="let marker of markers" [latitude]="marker.lat" [longitude]="marker.lang">
                <agm-snazzy-info-window [closeWhenOthersOpen]="true">
                    <ng-template>
                        <div class="row pop-over-content">
                            ...
                        </div>
                    </ng-template>
                </agm-snazzy-info-window>
            </agm-marker>
        </agm-marker-spider>
    </agm-marker-cluster>
</agm-map>

Works a treat ! Thank you

With this nested approach of cluster > spider, is there a way that when cluster has clicked, then it will spiderfy after? Thanks

Add OverlappingMarkerSpiderfier package

c3288cd

paulnagle mentioned this pull request Feb 25, 2018

Meetings Map spiderify paulnagle/NA-Ireland-Ionic-2#32

Open

sebholstein requested changes Mar 3, 2018

View reviewed changes

chancezeus force-pushed the master branch from 76a1f20 to 5a88c3d Compare March 3, 2018 20:52

Implement requested changes

edd30d8

chancezeus force-pushed the master branch from 5a88c3d to edd30d8 Compare March 3, 2018 20:52

- Add spiderfier to events

3b6dc37

- Replace google.maps types with corresponding @agm types

hernantomassini mentioned this pull request Apr 26, 2019

Overlapping Marker Spiderfier #1146

Closed

stale bot added the stale label May 9, 2019

stale bot closed this May 16, 2019

henryyue2010 mentioned this pull request Aug 9, 2019

how to set Spiderfier Marker's icon #1700

Closed

ghost reopened this Aug 9, 2019

stale bot removed the stale label Aug 9, 2019

stale bot added the stale label Nov 8, 2019

ghost added needs: adopter a PR that was abandoned, and needs to be cleaned up before merge and removed stale labels Nov 12, 2019

ghost closed this Jul 3, 2020

This pull request was closed.


		-----

		this package levereges the [npm-overlapping-marker-spiderfier][npm-overlapping-marker-spiderfier] to add spiderfy


		const markerPromise = this._markerManager.getNativeMarker(marker);

		this._markers.set(marker, markerPromise);

Add OverlappingMarkerSpiderfier package #1329

Add OverlappingMarkerSpiderfier package #1329

Conversation

chancezeus commented Feb 24, 2018

sebholstein left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

chancezeus Mar 3, 2018 • edited

Choose a reason for hiding this comment

chancezeus commented Mar 3, 2018

chancezeus commented Mar 12, 2018

chancezeus commented Mar 12, 2018

ChrisDevinePimss commented Mar 23, 2018

felberto commented Apr 20, 2018

Murali1689 commented May 4, 2018

Satheesh28 commented Jul 6, 2018

lam3rr commented Jul 27, 2018

WheelyWonka commented Sep 12, 2018

amorimdev commented Oct 2, 2018

amorimdev commented Oct 3, 2018

ChrisDevinePimss commented Oct 3, 2018 • edited

drjaat commented Oct 4, 2018

btimeteam commented Oct 5, 2018

Smiter15 commented Oct 8, 2018 • edited

ChrisDevinePimss commented Oct 8, 2018

Smiter15 commented Oct 8, 2018 • edited

ChrisDevinePimss commented Oct 8, 2018 • edited

Smiter15 commented Oct 8, 2018

AScheidt commented Oct 29, 2018

AScheidt commented Oct 29, 2018 • edited

rgails commented Jan 25, 2019

azurenote commented Feb 8, 2019

stale bot commented May 9, 2019

henryyue2010 commented Aug 9, 2019

stale bot commented Nov 8, 2019

CrackerakiUA commented Nov 18, 2019

ghost commented Nov 19, 2019

anotherboz commented Nov 26, 2019

CrackerakiUA commented Dec 2, 2019

albuquerquefabio commented Feb 20, 2020

CrackerakiUA commented May 7, 2020 • edited

shahabas-cp-14 commented May 8, 2020

albuquerquefabio commented May 20, 2020 • edited

Install as dev Dependencies

Install as Dependencies

At your tsconfig.app.json

ghost commented Jul 3, 2020

crac7 commented Apr 28, 2021 • edited

Install as dev Dependencies

Install as Dependencies

At your tsconfig.app.json

ffuf-ralphnival commented May 3, 2022

chancezeus Mar 3, 2018 •

edited

ChrisDevinePimss commented Oct 3, 2018 •

edited

Smiter15 commented Oct 8, 2018 •

edited

Smiter15 commented Oct 8, 2018 •

edited

ChrisDevinePimss commented Oct 8, 2018 •

edited

AScheidt commented Oct 29, 2018 •

edited

CrackerakiUA commented May 7, 2020 •

edited

albuquerquefabio commented May 20, 2020 •

edited

crac7 commented Apr 28, 2021 •

edited