#I'm noticing that dagger is updating my

1 messages · Page 1 of 1 (latest)

graceful blaze
#

👀 hm, dagger develop should still be required 🤔

onyx temple
#

Would it update on every call if that stage is never cached?

#

I tried this on:

  • 0.18.2 and now 0.18.6
  • With a fresh PHP module and now a fresh Go module
#

All I did, I changed:
From: func (m *Scratch) ContainerEcho(stringArg string) ...
To : func (m *Scratch) Echo(stringArg string) ...

dagger functions updates the name, without any call to dagger develop.

Similarly I tried changing the argument to an integer.
It updated it in the --help to say it was an integer.

# 
~/Documents/scratchblank $ dagger functions
✔ connect 0.3s
✔ load module 5.9s

Name             Description
container-echo   Returns a container that echoes whatever string argument is provided
grep-dir         Returns lines that match a pattern in the files of the provided Directory
~/Documents/scratchblank $ dagger functions
✔ connect 0.4s
✔ load module 5.7s

Name       Description
echo       Returns a container that echoes whatever string argument is provided
grep-dir   Returns lines that match a pattern in the files of the provided Directory
~/Documents/scratchblank $
graceful blaze
#

ohhh

#

yes

#

so, behind the scenes, dagger call/dagger functions is rerunning the codegen

#

but it's not outputting it to the client

#

i think this has always been the case (at least, as long as i can remember)

onyx temple
#

So, when do I need to run dagger develop?

graceful blaze
#

only when you want the results for your ide

onyx temple
#

Right I see... so as long as I make a call to dagger, it will update.
dagger develop is the equivalent of "I don't need to run a command, but update my codegen please"

glad tree
#

It didn't always do that; dagger develop was required at some points previously.

pine bough
#

As far back as I can remember, most dagger CLI commands have done the codegen automatically.