You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe 👀
This issue is related to: #5836, which is partially solved in existing PR.
Would like two things, type safety for back end plugins and for both front end and back end plugins to be bundled together, as they will more often then not be worked on together
Describe the solution you'd like 🎁
Expect back end plugins to be located in the same place as front end, in the same repository, thus they would need to be in front end 'common/plugins' when implemented, we can do the same thing as front end plugins, share webpack config and tsconfig, and expose types from back end view 'ts-link' crate.
The bundling cli should look in folders for both backend and front end plugins (but can of course can be pointed to an individual plugin)
Describe alternatives you've considered 💭
Additional context 💌
Moneyworks Jobcode 🧰
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe 👀
This issue is related to: #5836, which is partially solved in existing PR.
Would like two things, type safety for back end plugins and for both front end and back end plugins to be bundled together, as they will more often then not be worked on together
Describe the solution you'd like 🎁
Expect back end plugins to be located in the same place as front end, in the same repository, thus they would need to be in front end 'common/plugins' when implemented, we can do the same thing as front end plugins, share webpack config and tsconfig, and expose types from back end view 'ts-link' crate.
The bundling cli should look in folders for both backend and front end plugins (but can of course can be pointed to an individual plugin)
Describe alternatives you've considered 💭
Additional context 💌
Moneyworks Jobcode 🧰
The text was updated successfully, but these errors were encountered: