Handle both ferdi and ferdium servers for transferring from

[vraravam]

Pre-flight Checklist

1. Please remember that if you are logging a bug for some service that has stopped working or is working incorrectly, please log the bug here
2. If you are requesting support for a new service in Ferdium, please log it here
3. Please remember to read the self-help documentation - in case it helps you unblock yourself for issues related to older versions of recipes that were installed on your machine. (These will get automatically upgraded when you upgrade to the newer versions of Ferdium, but to get new recipes between Ferdium releases, this documentation is quite useful.)
4. Please ensure you've completed all of the following.

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Description of Change

When checking in pre-existing profiles whether Ferdium is being used without a server, we need to handle both Ferdi as well as Ferdium profiles.

Motivation and Context

Fixes comment from: #4 (comment)

Screenshots

Checklist

• My pull request is properly named
• The changes respect the code style of the project (npm run prepare-code)
• npm test passes
• I tested/previewed my changes locally

Release Notes

[SpecialAro]

Looks good, but I'm not exactly sure if it will suffice to solve the issue. Have you test it?

[real-or-random]

Hi, thanks for the quick attempt to fix this. I tested this with v6.0.0-nightly.100 and it does not work.

---

A quick code search shows that there is actually another code location where the magic string appears:

ferdium-app/src/config.ts

Line 185 in d3f2edf

export const LOCAL_SERVER = 'You are using Ferdium without a server';

This is used a few places (and should also been used in code that has been touched by this PR).

This location looks like a potential suspect:

ferdium-app/src/stores/SettingsStore.ts

Lines 59 to 62 in 71c5237

	server => {
	if (server === LOCAL_SERVER) {
	ipcRenderer.send('startLocalServer');
	}

There's a _migrate() function that's called before that code is reached. I suspect the right thing to do is to add code to this function that rewrites the old string to the new string. Or better, migrate all "You are using ... " some better than a magic string that contains the appname, maybe just the empty string.

If I change the string manually in the settings.json, then everything works. So apparently that setting is really the only culprint. So this should be a reliable way for you to test this. Or alternatively, this also suggests a simpler solution: add a line to the migration shell scripts that rewrites the config...

[vraravam]

Good catch and analysis @real-or-random - i will try to fix this later tonight