not sure I'm following @kalle can you expand?

So this creates default translate dynamicly, and now here I have diffrent value from

$activity->description

so existing translations fail and I need to add new keys.

ok I see, and you want to avoid publishing the entire twill lang file to add yours?

I mean if there is no better way Ill need to do that.

that's how Laravel works with lang files by default I think, I guess you're expecting the same behavior as Twill's config?

maybe it's possible, but yeah at the moment without code change you need the whole file

Yeah I dont think there is better way for now too. Maybe later we can create user lang config files which could be merged into existing Twill lang file dynamicly on fly for these use cases. Submitted request for this https://github.com/area17/twill/issues/1817 Let me know if Im wrong on something

Hey guys. How can I test if a package I built works or not??

well, does it work?

just kidding

do you mean to see if the install works through composer?

did you publish it to packagist?

To be clear. I built a functionality and I am able to convert this functionality into a package. Now I want to see if this package works for me or not. But in the same project I have both the functionality and the package

create a fresh twill project to install the package?

no, not yet. I will try it if it works or not

ok

I'm not sure what the package does, but you can probably comment or remove the code that's inside the app to make sure that it is the package code that is used in your app

ok,i will try

I removed the code that I had added and left only the package, but it does not work for me. The package contains a custom component (a crud table in which the emails of users who subscribe are displayed)

Totally unrelated to your issue but I don't think you'll want to use the area17 namespace for it

you won't be able to publish it to our name

Did you register your package custom components? did you rebuild twill assets?

hi, i have still problem with the custom vuejs development. I have now the 3.x branch from twill, so it is the newst codebase. If I run the twill:dev command, everythings seems ok, the dev server starts, but the system misses the manifest file

you have the dev mode enabled in your .env?

yes, it is set to true

I honestly do not know why it is not working for you 😦 if you run twill:build it does work?

yes

but if i set the dev mode to false, the page works

i will try a clean install with the 3.x branch, maybe something is broken in my codebase