[GH-ISSUE #116] Language/Translation Feature #87

New Issue

GiteaMirror · 2026-04-11T08:42:10-05:00

GiteaMirror commented

2026-04-11 08:42:10 -05:00

Originally created by @z3rodaycve on GitHub (Feb 5, 2026).
Original GitHub issue: https://github.com/reconurge/flowsint/issues/116

Hello,

I’d like to suggest adding Language/Translation feature so users can switch the UI language in Flowsint.
I’ve taken a look at React i18n (https://react.i18next.com), and if this sounds like a good idea, I’d be happy to implement it in the current build.

Additionally, I can create a Slovak (sk-SK) translation for Flowsint.

Originally created by @z3rodaycve on GitHub (Feb 5, 2026). Original GitHub issue: https://github.com/reconurge/flowsint/issues/116 Hello, I’d like to suggest adding Language/Translation feature so users can switch the UI language in Flowsint. I’ve taken a look at React i18n (https://react.i18next.com), and if this sounds like a good idea, I’d be happy to implement it in the current build. Additionally, I can create a Slovak (sk-SK) translation for Flowsint.

GiteaMirror commented

2026-04-11 08:42:11 -05:00

@dextmorgn commented on GitHub (Feb 10, 2026):

Hello @z3rodaycve,

Thanks you for this feature request.

I'm hesitating on this one. Do you think users would really benefit from this feature?

I feel most people would pretty much understand most of the english actions and texts in the app.

Feel free to challenge me on this, cause I don't really have an opinion. Obviously if more people think this is necessary then we'll implement it. :)

Open to discussion!

Thanks again

@dextmorgn commented on GitHub (Feb 10, 2026): Hello @z3rodaycve, Thanks you for this feature request. I'm hesitating on this one. Do you think users would really benefit from this feature? I feel most people would pretty much understand most of the english actions and texts in the app. Feel free to challenge me on this, cause I don't really have an opinion. Obviously if more people think this is necessary then we'll implement it. :) Open to discussion! Thanks again

GiteaMirror commented

2026-04-11 08:42:11 -05:00

@z3rodaycve commented on GitHub (Feb 11, 2026):

Hello,

I get your point that most people understand English, but I think many users would still prefer using the app in their native language.

Apart of that, I think implementing react-i18next early in development could save time in the future. Even if we don't translate Flowsint into multiple languages right away, having the core system in place would make adding translations later much easier.

One quick off topic question: does Flowsint accept contributions in the form of Flowsint enrichers? Are there any guidelines on what's worth implementing (e.g, country specific lookups like the company-lookup "SIREN" for France)?

Thanks!

@z3rodaycve commented on GitHub (Feb 11, 2026): Hello, I get your point that most people understand English, but I think many users would still prefer using the app in their native language. Apart of that, I think implementing react-i18next early in development could save time in the future. Even if we don't translate Flowsint into multiple languages right away, having the core system in place would make adding translations later much easier. One quick off topic question: does Flowsint accept contributions in the form of Flowsint enrichers? Are there any guidelines on what's worth implementing (e.g, country specific lookups like the company-lookup "SIREN" for France)? Thanks!

GiteaMirror commented

2026-04-11 08:42:12 -05:00

@dextmorgn commented on GitHub (Feb 11, 2026):

@z3rodaycve,

I think implementing react-i18next early in development could save time in the future.

You're definetly right on this : the sooner the better !

I'll add this to the roadmap.

does Flowsint accept contributions in the form of Flowsint enrichers?

Absolutly ! You can definetly propose enricher, that would be awesome. For now, no specific guideline has been defined : if you think your enricher is not too specific to a use case and can benefit the community, please feel free to make a pull request.

Thanks to @xhzeem great idea, in the future, I'd like to propose a hub of config based enrichers (yaml files) that anyone could create and share.

Example:

name: ip-lookup
category: Ip
version: 1.0
input:
  type: Ip
  key: address
request:
  method: GET
  url: http://ip-api.com/json/{{address}}
  timeout: 30
response:
  expect: json
  map:
    address: query
    country: country
    city: city
    latitude: lat
    longitude: lon
    isp: isp
output:
  type: Ip

That will likely highly simplify sharing and contributing.

@dextmorgn commented on GitHub (Feb 11, 2026): @z3rodaycve, > I think implementing react-i18next early in development could save time in the future. You're definetly right on this : the sooner the better ! I'll add this to the roadmap. > does Flowsint accept contributions in the form of Flowsint enrichers? Absolutly ! You can definetly propose enricher, that would be awesome. For now, no specific guideline has been defined : if you think your enricher is not too specific to a use case and can benefit the community, please feel free to make a pull request. Thanks to @xhzeem great idea, in the future, I'd like to propose a hub of config based enrichers (yaml files) that anyone could create and share. Example: ```yaml name: ip-lookup category: Ip version: 1.0 input: type: Ip key: address request: method: GET url: http://ip-api.com/json/{{address}} timeout: 30 response: expect: json map: address: query country: country city: city latitude: lat longitude: lon isp: isp output: type: Ip ``` That will likely highly simplify sharing and contributing.

GiteaMirror commented

2026-04-11 08:42:12 -05:00

@z3rodaycve commented on GitHub (Feb 11, 2026):

@xhzeem ‘s idea of config hub sounds really interesting - im really looking forward to its implementation.

If there’s anything I can help with regarding react-i18next, I’d be happy to assist.

Thanks again!

@z3rodaycve commented on GitHub (Feb 11, 2026): @xhzeem ‘s idea of config hub sounds really interesting - im really looking forward to its implementation. If there’s anything I can help with regarding react-i18next, I’d be happy to assist. Thanks again!

GiteaMirror commented

2026-04-11 08:42:13 -05:00

@dextmorgn commented on GitHub (Feb 23, 2026):

Hey @z3rodaycve,

If you want to work on an implementation of React i18n in the app, I'd be more than happy to review your work and propose a merge :)
It could be a good first issue.

Let me know !

@dextmorgn commented on GitHub (Feb 23, 2026): Hey @z3rodaycve, If you want to work on an implementation of React i18n in the app, I'd be more than happy to review your work and propose a merge :) It could be a good first issue. Let me know !

GiteaMirror commented

2026-04-11 08:42:13 -05:00

@z3rodaycve commented on GitHub (Feb 23, 2026):

Hey @z3rodaycve,

If you want to work on an implementation of React i18n in the app, I'd be more than happy to review your work and propose a merge :)
It could be a good first issue.

Let me know !

Sure! I would be more than happy to do so! Should I create a pull request when I am done?

Thank you :)

@z3rodaycve commented on GitHub (Feb 23, 2026): > Hey @z3rodaycve, > > If you want to work on an implementation of React i18n in the app, I'd be more than happy to review your work and propose a merge :) > It could be a good first issue. > > Let me know ! Sure! I would be more than happy to do so! Should I create a pull request when I am done? Thank you :)

GiteaMirror commented

2026-04-11 08:42:14 -05:00

@dextmorgn commented on GitHub (Feb 24, 2026):

Absolutly, you could create a PR that fixes this issue :)

@dextmorgn commented on GitHub (Feb 24, 2026): Absolutly, you could create a PR that fixes this issue :)

GiteaMirror referenced this issue

2026-04-11 08:43:20 -05:00

[PR #87] [MERGED] feat: autodiscover types and enrichers #137

GiteaMirror referenced this issue

2026-04-13 13:38:24 -05:00

[PR #87] [MERGED] feat: autodiscover types and enrichers #273

GiteaMirror referenced this issue