"–skip-validation" command will be deprecated?

App Platform
, ,
1

Good day. I kindly need an assistance on this one since we notice it earlier.

We like to confirm if this is indeed will deprecate on the Freshdesk FDK Custom App?

NOTE: The ‘–skip-validation’ option for app packaging will be deprecated by Sep 2024. Please fix the errors before Sep 2024.

I’ve using 9.2.0 on this one.

Here is my image:

Screenshot 2024-08-12 at 11.48.43 AM

We suspect that this we might have encounter build problems if we are gonna use fdk pack.

Can we have request for an alternative solution for this one? Since it will impact also future builds that we used currently (Highly important)

Thank you.

Regards,
Bryan

2

Hi @BrianDev,

We plan to deprecate this flag option to ensure all the validation errors are fixed before packing the app and submitting it.

Could you please elaborate on the issues that are preventing your build process from proceeding so that we can suggest alternatives?

3

Hi!

I’ll elaborate some issues here.

Our custom app right now is facing some warning errors that can impact our future builds pertains to this error validation which it would take time to adjust on our end.

Screenshot 2024-08-12 at 3.39.08 PM

Since this is the application that is build since then, we hope that we can’t encounter this the next time we need to build in the future.

Also, on the coverage scenario, I cannot pack to zip with our custom app since we encounter this issue also.

Screenshot 2024-08-12 at 3.40.41 PM

I taking note here that in 9.0.4 or 9.1.0, we didn’t encountered this to pack to zip file our apps with no issues.

The only way I could think of is to downgrade my FDK here from 9.2.0. Kindly confirm if this is possible as I have related thread to this one: Downgrade Freshdesk Version

Thank you.

Regards,
Bryan

4

Hi, Sir Raviraj.

This removed the warning upon downgrading FDK using the thread link that I’ve given, but I still need confirmation to this thread to make ensure we can plan early if possible with our leads.

I also raised it on this ticket.

https://dev-assist.freshworks.com/helpdesk/tickets/3547

Thank you.

5

I can confirm that this will be a problem for our company also. We develop custom apps for internal use only.

The following code checks are too restrictive:

  1. Code coverage > 80%
  2. Refrain from simply logging errors
  3. Function complexity limited to 7
6

Acknowledging this as we encountered this also on FDK 9.2.0. But on lower versions in version 9, this one doesn’t have the errors encountered while we use FDK Pack or Run commands.

7

@BrianDev The validation warnings will not be blockers for packing the app. Only the validation errors will block the app from being packed and published.

Please let us know if you have any errors that cannot be fixed, and we can try to address those feedback.

The code coverage requirement applies only to public apps published in the Freshworks marketplace for all customers. It does not apply to custom apps.
You can skip the code coverage requirement error with the flag from our documentation.

Hi @Don_Bigler,

  1. As I mentioned, the code coverage requirement applies only to public apps. Otherwise, it can be ignored with a flag for running and packing the app.
  2. I hope it is a warning. Validation errors will not be a blocker.
  3. I hope it’s also a warning and not a blocker.
1 Like
8

Hi everyone,

I want to point out that the “–skip-validation” is crucial to have for us as well. We are developing a lot of custom apps (and a couple of marketplace ones) using webpack, and due to the nature of how webpack works, we get a lot of errors/warnings on perfectly valid code. We will have to rewrite at least a dozen apps from scratch if the flag is fully deprecated, because as it stands, I already can’t update some of these apps without downgrading to an earlier version of FDK.

1 Like