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

improve some doc cohesion and fix generator->definitions README link #3373

Merged
merged 1 commit into from
Nov 25, 2023

Conversation

dillonstreator
Copy link
Contributor

No description provided.

@dillonstreator dillonstreator requested a review from a team as a code owner November 24, 2023 21:00
Copy link

vercel bot commented Nov 24, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
medplum-www ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 24, 2023 10:32pm
2 Ignored Deployments
Name Status Preview Comments Updated (UTC)
medplum-app ⬜️ Ignored (Inspect) Visit Preview Nov 24, 2023 10:32pm
medplum-storybook ⬜️ Ignored (Inspect) Visit Preview Nov 24, 2023 10:32pm

Copy link

vercel bot commented Nov 24, 2023

@dillonstreator is attempting to deploy a commit to the Medplum Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

sweep-ai bot commented Nov 24, 2023

Apply Sweep Rules to your PR?

  • Apply: All new business logic should have corresponding unit tests.
  • Apply: Refactor large functions to be more modular.
  • Apply: Add docstrings to all functions and file headers.

@@ -23,7 +23,7 @@ When considering which option is best for you, we must consider some system char
- How easy or difficult is it to modify the existing system?
- Are engineers actively updating the existing system?
- How frequently does the existing system deploy new releases?
- Is the existing system stable, or are changes avoided?
- Is the existing system stable, or is change frequent?
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm not entirely confident that this change accurately captures the original intention, but it seems the intention was to convey opposites. In my view, a "stable system" typically implies avoiding changes.

I suppose this is context-dependent; for instance, when discussing the stability of an API, frequent change may suggest lower stability. On the other hand, in the context of internal component modifications, updates could potentially enhance stability.

@codyebberson codyebberson added this pull request to the merge queue Nov 25, 2023
Merged via the queue into medplum:main with commit bdb0d6a Nov 25, 2023
12 checks passed
@reshmakh reshmakh added this to the November 30, 2023 milestone Dec 1, 2023
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.

None yet

3 participants