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
Currently, the only validation the frontend performs is that the destination URL is a valid URL.
We can help users avoid typing the wrong URLs by performing more validations in the frontend before persisting the destination.
Examples of possible additional validations:
and many more, we can probably think of a better validation for every destination.
The first step in implementing this issue may be just validating a single destination in addition to thinking about a good design for validations in frontend.
The text was updated successfully, but these errors were encountered:
Hi @edeNFed , is this issue still open? I will like to pick it up and resolve it. I am more interested about FE related issues on Open Source projects!
I was able to come up with an FE validation for the Elasticsearch and Generic OTLF urls.
Implementation was based on testing the URLs on the frontend against a regex pattern
Currently, the only validation the frontend performs is that the destination URL is a valid URL.
We can help users avoid typing the wrong URLs by performing more validations in the frontend before persisting the destination.
Examples of possible additional validations:
9200
4317
The first step in implementing this issue may be just validating a single destination in addition to thinking about a good design for validations in frontend.
The text was updated successfully, but these errors were encountered: