Deprecated ww functions & upcoming improvements to the dev experience

Developer corner
1

Hi there dear devs :grinning:

Some of you may have noticed already: since the big Summer Update yesterday, some ww functions have been deprecated.

What does that mean?

You’ll see warnings in the console to inform you that a function is deprecated, but there will be no impact on your existing apps for now. Everything will work as it did prior to the release.

There will be an impact in the future but we don’t know when exactly. Of course, we’ll inform you in advance when there might be a breaking change and provide as much info as possible to help you with the transition.

This is basically a first step to improve the dev experience for all of you :slightly_smiling_face:

You may have seen some improvements in the “Coded components” tab of the WeWeb dashboard and inside the “Dev” editor. There’s a lot more coming!

Next up:

  1. Simplified way of building a plugin.
  2. Ability to share/sell plugins on the marketplace.
  3. New dev docs! Yeyyyy :partying_face:

I can’t share an ETA yet because it’s still early days but know that the team has already started work on item #1 and is expected to start work on items #2 and 3 in August.

3 Likes
2

can we have a list of the deprecated functions?

3

Deprecated and moved functions

  • wwLib.goTo => wwLib.wwApp.goTo
  • wwLib.getStyleFromToken => wwLib.wwUtils.getStyleFromToken
  • wwLib.getTypoFromToken => wwLib.wwUtils.getTypoFromToken
  • wwLib.element => Deprecated
  • wwLib.resolveObjectPropertyPath => wwLib.wwUtils.resolveObjectPropertyPath
  • wwLib.getTextStyleFromContent => wwLib.wwUtils.getTextStyleFromContent
  • wwLib.executeWorkflow => wwLib.wwWorkflow.executeGlobal
  • wwLib.findParentUidByFlag => wwLib.wwEditor.findParentUidByFlag
  • wwLib.selectParentByFlag => wwLib.wwEditor.selectParentByFlag
  • wwLib.useCreateElement => wwLib.wwElement.useCreate
  • wwLib.useLayoutStyle => wwLib.wwElement.useLayoutStyle
  • wwLib.wwCollection.getCollectionData => wwLib.wwUtils.getDataFromCollection
  • wwLib.wwUtils.getUniqueId => wwLib.wwUtils.getUid
  • wwLib.wwUtils.addScriptToHead => wwLib.wwApp.addScriptToHead
  • wwLib.wwUtils.getSelectedComponent => wwLib.wwEditor.getSelectedComponent
  • wwLib.wwUtils.scrollIntoView => wwLib.wwApp.scrollIntoView
  • wwLib.wwWebsiteData.getWebsiteName => Deprecated
  • wwLib.wwWebsiteData.getDesign => Deprecated
4 Likes
4

I’ve never used any of those functions nor do I have any custom-coded components. However, I do get warning logs for wwLib.getTextStyleFromContent. Should I be concerned about this?

image
image1396×79 6.74 KB

5

No worries, WeWeb’s native components use some of the methods. So if you’re not using it, you can just ignore it, they will fix it on their side.

1 Like
6

Where all available WeWeb functions can be found. In the documentation it doesn’t seem to have it yet.

7

thanks, appreciate the list.

1 Like
8

How should we go about access the app.vue when building our components?

9

Nowhere for now :smiley:

It was private and we provided some of them to the community as a workaround for edge case we didn’t handle yet.

We are in the process of defining what we want to make public and support on the long term, we make the signature of our methods more uniform, clear many things, when ready we will release a complete documentation to help you build with theses functions!

2 Likes