cancel
Showing results for 
Search instead for 
Did you mean: 

Powerapps Checker custom patterns

I like the powerapps checker to validate solution components against upgradeability, performance pattern etc.

 

I would like to have the possibility to add custom pattern which extends the validation checks. It would provide us the possibility to validate our own guidelines in addition to the Microsoft pattern.

 

Status: New

@LarsMartin, thanks for the suggestion. We have actually heard this a few times, but would love some additional details to gain an understanding of the recommendation. We have five classifications of checks:

  1. .NET code (plug-ins or workflow activities)
  2. Web language (JavaScript)
  3. Metadata
  4. App checker for embedded canvas apps
  5. Flow checker for embedded Flow definitions

Which are you looking to add? Can you provide some concrete examples? These would be extremely helpful. I'm wondering if we could provide you with some "parameterized" or PowerApps formula based approach to adding checks, which would make things much easier for you to author rules. Also, any way that you could provide a little more detail on the value that it would add to you?

 

Note - if these are JavaScript or TypeScript items, then we will be providing a mechanism to validate and extend ESLint very soon.

 

@AengusHeaney 

Comments
PowerApps Staff
Status changed to: Under Review
 
PowerApps Staff
Status changed to: New

@LarsMartin, thanks for the suggestion. We have actually heard this a few times, but would love some additional details to gain an understanding of the recommendation. We have five classifications of checks:

  1. .NET code (plug-ins or workflow activities)
  2. Web language (JavaScript)
  3. Metadata
  4. App checker for embedded canvas apps
  5. Flow checker for embedded Flow definitions

Which are you looking to add? Can you provide some concrete examples? These would be extremely helpful. I'm wondering if we could provide you with some "parameterized" or PowerApps formula based approach to adding checks, which would make things much easier for you to author rules. Also, any way that you could provide a little more detail on the value that it would add to you?

 

Note - if these are JavaScript or TypeScript items, then we will be providing a mechanism to validate and extend ESLint very soon.

 

@AengusHeaney 

Level: Powered On

@MikeHuguet 

Please find below some example of our guidelines:

2019-09-13 12_19_50-Project_Internal_CodeReview_Detail_YYYYMMDD  -  Schreibgeschützt - Excel.png

I guess some of them can be describe as patterns the code could be checked for.

In addition a colleague imagine following example rules:

  • use Promise instead sync. Request
  • use „const/let“ instead „var“ for JS-Developing

In case you need more details please contact sven.honert@orbis.de. 

PowerApps Staff

Hey @LarsMartin these are great examples. Thanks for posting. Have you run PowerApps checker via the PowerShell module or the Azure DevOps task? Try the AppSource Certification ruleset. It actually has a number of these same rules. We don't include all of our rules in the Solution Checker ruleset because they can emit a lot of noise, such as the DOM acccess rule. The last thing that we wanted to do with our first feature to the world was to emit a lot of noise. Take a look at the rules included via our web API endpoint.  We actually have others beyond this ruleset that are even more noisy that we'll be evaluating in the near future to see if we can reduce the noise. We even have some rules not listed in the public view that we are leveraging internally, such as comparison of a patch solution to a base solution looking for changes that are known to cause update issues. We'll take a look at some of these to see if we can turn them on for you, if we have them, as this would be faster than a feature to let you provide your own rules. We'll also take a look at this list to see if there are some that we can add for you as well. No promises though. Smiley Wink Keep the feedback coming!

 

For more details on our APIs see: https://docs.microsoft.com/powerapps/developer/common-data-service/checker/webapi/overview

 

View the rulesets: http://unitedstates.api.advisor.powerapps.com/api/ruleset

View the rules for the AppSource Certification ruleset: https://unitedstates.api.advisor.powerapps.com/api/rule?ruleset=083a2ef5-7e0e-4754-9d88-9455142dc08b

View all of the rules available to the public: https://unitedstates.api.advisor.powerapps.com/api/rule

Level: Powered On

@MikeHuguet 

I use the PowerApps Checker via AzureDevops and so far I used the "Solution Checker" option instead of the "Appsource certification". 

Thank you for providing the rulesets. Its much clearer now what is checked in the background.

 

Looking forward to the next PowerApps Checker versions. We like it and use it.

PowerApps Staff

@LarsMartin great to hear. It seems as if we should write a blog (or promote someone such as yourself to do so Smiley Wink ) regarding two important customizations to the analysis pipeline: 1) changing rulesets and specifying rules and 2) setting exclusions. I'll talk it over with our PM, @AengusHeaney.

 

Thanks again!