Is it possible to url encode with mavo?

[GalinhaLX]

Hi

How can I url encode a url with mavo? Does mavo have a function for it?

Let's say I have a property value which is:
https://mavo.io/docs/storage#url-params

and I want it to become like this:
https%3A%2F%2Fmavo.io%2Fdocs%2Fstorage%23url-params

[DmitrySharabin]

For now, there is no way to do it, unfortunately. However, there is an open issue #762 about that. So, feel free to share your thoughts and usecases there.

[GalinhaLX]

the same way @LeaVerou is using on her demo:

html
<a property="url">[getWebsite(url)]</a>

_ & javascript_

function getWebsite(url) {
	return !!Mavo.value(url) ? new URL(url).host.replace(/^www\./, "") : "(Website)";
}

Isn't there a way to use the javascript function called encodeURIComponent() ?

Without knowing javascript I tried

function getWebsite(url) {
	return !!Mavo.value(url) ? new URL(url).host.encodeURIComponent() : "(Website)";
}

doesn't work, maybe it needs something between ( and )

Or is this a totally wrong way? :(

[GalinhaLX]

Hi

It's mentioned in this page in v.0.2.2 , breaking changes:
Note that if you're using custom JS functions in your expressions, those will continue to work fine, since function calls are perfectly valid MavoScript.
But I agree it would be better to put it in main documentation

[DmitrySharabin]

I would swear it was mentioned somewhere in the docs but I cannot find it. @DmitrySharabin do you remember where it is? And if it's not there, we should definitely mention it!

You are absolutely right. There was a mention in the docs before we released v0.2.2 (as @GalinhaLX mentioned). I checked the commits to the docs. Those are the ones with the corresponding changes: mavoweb/mavo.io@4fb0087 and mavoweb/mavo.io@803af57.

In those commits we removed the following sentences from two sections in the docs:

1. If a Mavo expression is more advanced than MavoScript, it is automatically parsed as JavaScript, allowing experienced web developers to do more with Mavo expressions.
2. Since MavoScript does not support comments, an easy way to force JS mode is a /* js */ comment in the start or end of the expression.

What do you think if we add something like this?

If you need something more advanced, you can invoke custom JavaScript functions (both synchronous and asynchronous) in your expressions. Function calls are perfectly valid MavoScript.

We can add it after the table here and here. Or anywhere else?

Thoughts?

[DmitrySharabin]

What do you think if we add something like this?
If you need something more advanced, you can invoke custom JavaScript functions (both synchronous and asynchronous) in your expressions. Function calls are perfectly valid MavoScript.
We can add it after the table here and here. Or anywhere else?

Ping @LeaVerou. :) What do you think? Can we add this ☝🏻 phrase to the docs?

[WebMechanic]

We can add it after the table here and here.

that's where I looked and would also expect such information :D

[LeaVerou]

LGTM. We may also want to use this (URL encoding) as an example.

[GalinhaLX]

It SUPER helps ! Thank you so much @DmitrySharabin

Wow ...even more simple than I thought

I ❤️ Mavo :)

[karger]

We may have removed this because there's been some discussion of *not* allowing arbitrary js in mavo expressions?

…

On 6/28/2022 7:48 PM, Dmitry Sharabin wrote: I would swear it was mentioned somewhere in the docs but I cannot find it. @DmitrySharabin <https://github.com/DmitrySharabin> do you remember where it is? And if it's not there, we should /definitely/ mention it! You are absolutely right. There was a mention in the docs before we released v0.2.2 (as @GalinhaLX <https://github.com/GalinhaLX> mentioned). I checked the commits to the docs. Those are the ones with the corresponding changes: ***@***.*** <mavoweb/mavo.io@4fb0087> and ***@***.*** <mavoweb/mavo.io@803af57>. In those commits we removed the following sentences from two sections in the docs: 1. If a Mavo expression is more advanced than MavoScript, it is automatically parsed as JavaScript, allowing experienced web developers to do more with Mavo expressions. 2. Since MavoScript does not support comments, an easy way to force JS mode is a |/* js */| comment in the start or end of the expression. What do you think if we add something like this? *If you need something more advanced, you can invoke custom JavaScript functions (both synchronous and asynchronous) in your expressions. Function calls are perfectly valid MavoScript.* We can add it after the table here <https://mavo.io/docs/mavoscript#mavoscript-vs-javascript> and here <https://mavo.io/docs/expressions#mavoscript-vs-javascript>. Or anywhere else? Thoughts? — Reply to this email directly, view it on GitHub <#859 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIWSXSZMHVS272CPUEDQD3VRMUHTANCNFSM5XBTXIMA>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[DmitrySharabin]

Yes, IIRC that was the reason.

[LeaVerou]

We don't allow arbitrary JS syntax in Mavo expressions, but we do allow any arbitrary function.

[qorncat]

Ye if you have 🐮 Boy

[qorncat]

lets do this