Am I missing something? In the generated docs, I can't see any of the custom Power Fx code? #188
Unanswered
TickboxPhil
asked this question in
Q&A
Replies: 1 comment 1 reply
-
|
Hi Phil, the latest version includes a range of improvements that reduce the overall size of Word documents. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Even with the "changes only" option, the generated docs are too verbose to be of real use for documenting the Power FX code - each bit is buried away inside some other HTML in Behaviour, with all the line breaks stripped - so almost unreadable:
Then each section is too big and verbose to compare code between controls/objects. It's 955 pages in Word for a small app! Unworkable, not to mention Word crashing even on a 64GB RAM machine. All that just to see the Power FX code?
It's a gap because "View Code" in Power Apps itself does show the Power Fx code, but it's swallowing up in 50 pages of JSON per screen - unusable (although 5 screens = 250 pages so a quarter of this system!). That's why I'm looking here. But similar problem it turns out.
Perhaps I'm missing a way of getting rid of all the fairly useless stuff? But the Power Fx code needs to be clearer anyway it seems.
Beta Was this translation helpful? Give feedback.
All reactions