Implementing function get_measures_list

[viktor-taraba]

Desired functionality:

A function that given the name of a report returns a list of measures used in it, along with information about:

• the table in which each measure is created
• the measure name
• its definition (DAX expression)

The output should be available in different formats (e.g., tabular view, Excel file, etc.).

Purpose:

• To implement functionality that is not available in this form in Power BI, but is useful during report development - especially when refining or optimizing existing reports.
• To analyze dependencies between measures and identify unused ones - this is important for optimization, and for understanding the impact of removing or modifying measures (perhaps will be done as a separate function with more details about dependencies).

[viktor-taraba]

in progress, plan to finish today

[viktor-taraba]

Created first version of get_measures_list in my forked repo:
implement get_measures_list: https://github.com/viktor-taraba/powerbpy_dev/blob/add_get_measures_list/src/powerbpy/get_measures_list.py
reference: https://github.com/viktor-taraba/powerbpy_dev/blob/add_get_measures_list/docs/reference/get_measures_list.qmd

[viktor-taraba]

@Russell-Shean Hi, could you give a hint regarding html docs in the repo for the website (like this one: https://github.com/Russell-Shean/powerbpy/blob/main/docs/docs/reference/create_blank_dashboard.html)? They seem to be generated based on the .qmd documentation files, but I am not sure how exactly (using R perhaps)

[Russell-Shean]

@viktor-taraba Thank you so much for this addition! It looks super useful. Let me know when you think it's ready to merge!

The documentation is created using a tool called quartodoc. Here's a link to the repo: https://github.com/machow/quartodoc

The overall website is defined here in this yaml file: https://github.com/Russell-Shean/powerbpy/blob/main/docs/_quarto.yml

The document rendering is triggered automatically by this github action: https://github.com/Russell-Shean/powerbpy/blob/main/.github/workflows/publish-quarto-docs.yml

quartodoc pulls the documentation automatically from the docstrings for each function. The documentation is honestly still a bit of a mess hahah. I started this project using readthedocs and sphinx and then later changed to using readthedocs. I still haven't updated most of the documentation to use markdown instead of sphinx.

Here's an example of a function that seems to be better formatted than the others: https://github.com/Russell-Shean/powerbpy/blob/main/src/powerbpy/create_blank_dashboard.py. It should be possible to use normal markdown to format the docstrings and quartodoc will automatically generate the documentation. The only other thing that needs to be done outside of the docstring is update the _quarto.yml file.