Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TRUNK-4004: Expose start_before_modules functionality better #4575

Merged
merged 1 commit into from
Mar 6, 2024

Conversation

ibacher
Copy link
Member

@ibacher ibacher commented Mar 6, 2024

Description of what I changed

TRUNK-4004 (#923) added extremely useful functionality to allow modules to declare that the need to start before any arbitrary modules. However, the existence of this feature was never exposed through the DTDs and there were no tests for the parser for this feature, so this commit rounds things out a bit.

A note on the implementation:

To get the DTD to work without going absolutely insane, the DTD actually declares the support for start_before_module as opposed to the original module. The support for start_before_module is added in this PR, so in older versions it may be necessary to use the module key instead of start_before_module. (The issue is that DTDs have a hard time with namespacing and the root element of config.xml is already called module).

Issue I worked on

see https://issues.openmrs.org/browse/TRUNK-

Checklist: I completed these to help reviewers :)

  • My IDE is configured to follow the code style of this project.

    No? Unsure? -> configure your IDE, format the code and add the changes with git add . && git commit --amend

  • I have added tests to cover my changes. (If you refactored
    existing code that was well tested you do not have to add tests)

    No? -> write tests and add them to this commit git add . && git commit --amend

  • I ran mvn clean package right before creating this pull request and
    added all formatting changes to my commit.

    No? -> execute above command

  • All new and existing tests passed.

    No? -> figure out why and add the fix to your commit. It is your responsibility to make sure your code works.

  • My pull request is based on the latest changes of the master branch.

    No? Unsure? -> execute command git pull --rebase upstream master

Note: For versions of OpenMRS without this commit, you must use a module
element as a child of the start_before_modules element.
@coveralls
Copy link

Coverage Status

coverage: 64.699% (-0.003%) from 64.702%
when pulling 9831e04 on TRUNK-4004
into 4f99a34 on master.

Seremba pushed a commit to Seremba/openmrs-core that referenced this pull request Mar 13, 2024
Wandji69 pushed a commit to Wandji69/openmrs-core that referenced this pull request Mar 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants