cancel
Showing results for 
Search instead for 
Did you mean: 

Share your ideas and vote for future features

Status: New
Status: New
  • PowerApps Build Tools
Status: New
  • PowerApps Build Tools
Status: New
Status: New
  • PowerApps Build Tools
Status: New
Status: New
  • PowerApps Build Tools
Status: New
  • PowerApps Build Tools
Status: New
  • PowerApps Build Tools
Status: New
  • PowerApps Build Tools
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 

  • PowerApps Build Tools
Status: New
  • PowerApps Build Tools
Status: New
Status: New
Status: New
Status: New
Status: New
Status: New
  • PowerApps Build Tools
Status: New
Status: New
  • PowerApps Build Tools
Labels