Clarify HTML Form Entry compatibility with OpenMRS 3 SPA

[vishal-ram-cs]

Added important note regarding HTML Form Entry compatibility with OpenMRS 3 (SPA) users.

Description of what I changed

Issue I worked on

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

Checklist: I completed these to help reviewers :)

• My pull request only contains ONE single commit
  (the number above, next to the 'Commits' tab is 1).

  No? -> read here on how to squash multiple commits into one

• 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

[vishal-ram-cs]

Hi maintainers 👋

I added a short clarification in the README to make it explicit that HTML Form Entry currently works with the Legacy UI / Reference Application and not with OpenMRS 3 SPA.

This came up while trying to verify an older Jira issue, where the demo instance loads a blank SPA or returns HTTP 500 errors, which can confuse users attempting to edit HTML forms.

Please let me know if you’d like any wording changes or a different placement in the documentation. Thanks!

[vishal-ram-cs]

Hi maintainers 👋

I added a short clarification in the README to make it explicit that HTML Form Entry currently works with the Legacy UI / Reference Application and not with OpenMRS 3 SPA.

This came up while trying to verify an older Jira issue, where the demo instance loads a blank SPA or returns HTTP 500 errors, which can confuse users attempting to edit HTML forms.

Please let me know if you’d like any wording changes or a different placement in the documentation. Thanks!

[mseaton]

Well, it's not entirely accurate. One can render html forms in O3 in an iFrame, which is supported and done by groups in production. It is true that any jsps written in htmlformentry to manage or view forms require legacyui, but that is not really any different almost every openmrs module.