Skip to content

Conversation

@Ang-m4
Copy link
Contributor

@Ang-m4 Ang-m4 commented Jun 10, 2025

Description

This PR corrects the behavior of the --output-token-references option so it properly toggles token-reference output, and adds support for the existing --exclude-core feature in the Python CLI binding.

Key Changes

  • Fix --output-token-references

    • Converted from a one-way flag into a true boolean toggle (--output-token-references/--no-output-token-references), with references enabled by default.
  • Add support for --exclude-core

    • Introduce a new --exclude-core flag to the paragon-build-tokens command, giving users the option to omit the core token set from the build output.

All related function docstrings, CLI help text, and README examples have been updated to reflect these changes.

- Add --exclude-core option to the build command
- Change token references option to --output-token-references/--no-output-token-references
- Update help text and argument handling accordingly
@openedx-webhooks openedx-webhooks added the open-source-contribution PR author is not from Axim or 2U label Jun 10, 2025
@openedx-webhooks
Copy link

Thanks for the pull request, @Ang-m4!

This repository is currently maintained by @arbrandes.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

  • If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
    • This process (including the steps you'll need to take) is documented here.
  • If it doesn't, simply proceed with the next step.
🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

  • Dependencies

    This PR must be merged before / after / at the same time as ...

  • Blockers

    This PR is waiting for OEP-1234 to be accepted.

  • Timeline information

    This PR must be merged by XX date because ...

  • Partner information

    This is for a course on edx.org.

  • Supporting documentation
  • Relevant Open edX discussion forum threads
🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details
Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

  • The size and impact of the changes that it introduces
  • The need for product review
  • Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

Copy link
Contributor

@brian-smith-tcril brian-smith-tcril left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left one comment with a specific question, but seeing this does make me wonder if manually wrapping the Paragon CLI this much makes sense.

With this pattern every time the Paragon CLI is updated to add a new option this plugin will need to be updated to wrap that option. That doesn't feel ideal to me.

Would it be possible to simplify the wrapper to just pass the Paragon CLI args through unmodified?

@mphilbrick211 mphilbrick211 moved this from Needs Triage to In Eng Review in Contributions Jun 12, 2025
@Ang-m4
Copy link
Contributor Author

Ang-m4 commented Jun 16, 2025

@brian-smith-tcril, thanks for your comments! I’ve simplified the paragon-builder command as you suggested, so it now forwards all arguments and options unchanged. This also means our tests in #36 no longer need to validate each flag or argument that belongs in Paragon’s own test suite.

Let me know what you think!

@Ang-m4 Ang-m4 requested a review from brian-smith-tcril June 16, 2025 17:42
@brian-smith-tcril
Copy link
Contributor

I’ve simplified the paragon-builder command as you suggested, so it now forwards all arguments and options unchanged

That's wonderful! Thank you!

This also means our tests in #36 no longer need to validate each flag or argument that belongs in Paragon’s own test suite.

I think the spirit of integration testing would imply we should still test arguments we expect users to use. We already have tests on the Paragon side for this, but verifying that nothing breaks when running the commands through the plugin still feels like a good thing for the plugin to have tests for.

Copy link
Contributor

@brian-smith-tcril brian-smith-tcril left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great! I'm really happy to see how much simpler this can be when just forwarding the args.

I left a comment about the docs, once that's addressed this should be good to merge!


- ``--output-token-references``
Include references for tokens with aliases to other tokens in the build output.
- ``--output-token-references/--no-output-token-references``
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of having a full list of available options that get passed through to the paragon CLI it might make sense to just link to the Paragon CLI docs (https://github.com/openedx/paragon/?tab=readme-ov-file#paragon-cli). If there's something you feel should be documented that isn't documented on the Paragon repo I'll gladly approve a PR adding it!

@Ang-m4 Ang-m4 force-pushed the afg/fix-paragon-flags branch from 470536b to 9d61529 Compare June 16, 2025 18:20
Copy link
Contributor

@brian-smith-tcril brian-smith-tcril left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is perfect! Thank you so much for working through the review process with me!

@brian-smith-tcril brian-smith-tcril merged commit da690fd into openedx:main Jun 16, 2025
3 checks passed
@github-project-automation github-project-automation bot moved this from In Eng Review to Done in Contributions Jun 16, 2025
@Ang-m4 Ang-m4 deleted the afg/fix-paragon-flags branch June 30, 2025 18:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

open-source-contribution PR author is not from Axim or 2U

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants