Wasp•17mo ago

Worth Moving to the Current State of Open SaaS?

My project is nearing its end. I started about mid June. What do authors think? Are the changes going to add significant value / security / ease of use etc.? Effort would be migrating client, actions, main.wasp (already manually migrated to wasp 0.14), schema, package.json etc. basically I'd think it'd be mostly copy and paste. Opinions?

kapa.ai•8/23/24, 7:30 PM

Hi @neogeofun. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

kapa.ai•8/23/24, 7:30 PM

----------------------
Hmm, I don't know enough to give you a confident answer yet. The decision to migrate to the current state of Open SaaS depends on various factors such as the specific needs of your project, the features you require, and your comfort level with the changes in the new version.

From the knowledge sources provided, it's clear that Wasp has undergone significant changes in its project structure from version 0.11.x to 0.12.0. The main differences include the removal of the server/client code separation, changes in the way external imports in your Wasp file are handled, and the introduction of a top-level

public

public

directory. These changes could potentially simplify your project structure and offer more flexibility in how you organize your code. However, it would require you to update your codebase to work with the new version of Wasp.

If you decide to migrate, Wasp provides detailed instructions and even scripts to help with the migration process. However, it's important to note that you might encounter breaking changes and you would need to fix these manually.

Before making a decision, I recommend reviewing the migration guide (https://wasp-lang.dev/docs/migrate-from-0-11-to-0-12#migrating-your-project-to-the-new-structure) and the overview docs (https://wasp-lang.dev/docs/tutorial/project-structure) to understand the new structure in detail. This will help you assess the effort required for migration and whether the new features and changes align with your project requirements.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•8/23/24, 7:30 PM

Sorry @neogeofun, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:

Perhaps try again in 15mins?

miho•8/26/24, 9:28 AM

One for you @Vinny (@Wasp)

Vinny•8/26/24, 9:35 AM

Our. advice is to check out the github repo and see for yourself where code has significantly changed. Then you can decide for yourself if its worth updating certain parts manually (e.g. copy-paste). Because you've made significant changes to your app in order to customize it, unless there are certain aspeects of the code that are problematic for you -- or annoy you -- It probably isn't necessary to update anything, especially if you're happy with the state your app is in

Filip•8/26/24, 12:47 PM

Hey @neogeofun, what Vinny said

Also, here's what I told another user, it might help your decision: Migration to 14, should update auth field?

Worth Moving to the Current State of Open SaaS?

Similar Threads

Similar Threads

Similar Threads