Allgemein

3. February 202214. February 2022

Mutmaßlicher Betrug und/oder Diebstahl bei Amazon Retouren

Wie ich so lese bin ich kein Einzelfall.

Ich hatte im Dezember u.a. einen Amazon FireTV Stick bestellt und einen FireTV LAN Adapter.
Der LAN Adapter hat nicht funktioniert und dieser FireTV Stick ist eine Zumutung.
Beide kamen im selben Versandkarton an.
Continue reading “Mutmaßlicher Betrug und/oder Diebstahl bei Amazon Retouren”

6. January 20226. January 2022

I’m seeking remote work as a Go / Golang and/or Vue or Angular Backend or Full Stack Developer

Hello potential employer or contractor,

I’m seeking remote only paid work, 20-40 hours / week.
No job agencies.

I’m available as a contractor or as an employee.
My location in winter is Göppingen, Germany – in summer Rijeka, Croatia.
I’m registered in Germany, that’s also where my business is registered.

I currently only have a resume up in German at https://resume.icod.de/

You can also get in touch via comments or https://icod.de/kontakt

6. January 20226. January 2022

Keycloak upgrade to 16.1.0 standalone

Upgrading Keycloak to 16.1.0 is not straightforward, it requires manual hands, especially if you’re behind a nginx proxy or other reverse proxy.

The documentation has some vague hints that sends you to dead ends.

I wrote a little upgrade script for my keycloak upgrades
Continue reading “Keycloak upgrade to 16.1.0 standalone”

29. November 202118. October 2022

Crayon Syntax Highlighter Updated for PHP 8

I have updated the Crayon Syntax Highlighter to work with PHP8 and above.
While I have tagged the release as 2.8.6 I’m moving away from that version scheme.

cd wp-content/plugins/
git clone https://code.icod.de/dalu/crayon-syntax-highlighter.git

1 2	cd wp-content/plugins/ git clone https://code.icod.de/dalu/crayon-syntax-highlighter.git

and use master branch.

Remember to visit the settings page and save your settings, especially when switching PHP versions.

To my knowledge this is the only public repository of a working Crayon Syntax Highlighter plugin, feel free to correct me.

22. October 2021

Quasar v2 create re-usable js file with vue3

I had a little problem migrating Quasar v1 to v2. I wanted to have a re-usable (importable) .js file that I could import in every SFC.
This particular case used i18n.

I create a directory lib under the src dir.
Since this .js file was to set the default menu items in every SFC I named it defaultItems.js.
So it lives in src/lib/defaultItems.js

The content of the file

import { useStore } from 'vuex'
import { useI18n } from 'vue-i18n';

export default function () {
  const i18n = useI18n()
  const items = [
    {
      label: i18n.t('sidebar.home'),
      to: {path: '/'}
    },
    {
      label: i18n.t('sidebar.feed'),
      to: {path: '/feed/'}
    },
    {
      label: i18n.t('sidebar.groups'),
      to: {path: '/groups/'}
    }
  ]
  const store = useStore()
  store.dispatch('sideMenu/setItems', items)
}

import { useStore } from 'vuex'

import { useI18n } from 'vue-i18n';

export default function () {

const i18n = useI18n()

const items = [

{

label: i18n.t('sidebar.home'),

to: {path: '/'}

{

label: i18n.t('sidebar.feed'),

to: {path: '/feed/'}

{

label: i18n.t('sidebar.groups'),

to: {path: '/groups/'}

}

]

const store = useStore()

store.dispatch('sideMenu/setItems', items)

}

You see a bunch of things.

import { useStore } from 'vuex'
and
import { useI18n } from 'vue-i18n';

Vue3 has this new use* functions that allow for instance vuex to be accessed via useStore() or vue-i18n to be accessed via useI18n() anywhere.

So that’s pretty simple.

You can now import the defaultItems.js file in your SFC.

<script>
import defaultItems from 'src/lib/defaultItems';

export default defineComponent({
  name: 'PageIndex',
  mounted() {
    defaultItems()
  }
})
</script>

import defaultItems from 'src/lib/defaultItems';

export default defineComponent({

name: 'PageIndex',

mounted() {

defaultItems()

}

})

</script>

Of course now that I see this, it’s wrong to store the translated text in the vuex store. Only the references should be stored there and the translation should happen in the display component.
e.g. the label shouldn’t be i18n.t(‘sidebar.home’) but only ‘sidebar.home’ and later do $t() or <v-t> in the component