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

refactor(patterns): Prepare for compression #2248

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

erights
Copy link
Contributor

@erights erights commented Apr 29, 2024

closes: #XXXX
refs: #XXXX

Description

Security Considerations

Scaling Considerations

Documentation Considerations

Testing Considerations

Compatibility Considerations

Upgrade Considerations

  • Includes *BREAKING*: in the commit message with migration instructions for any breaking change.
  • Updates NEWS.md for user-facing changes.

@erights erights self-assigned this Apr 29, 2024
@erights erights force-pushed the markm-prepare-for-extended-matchers branch from 1943903 to 896cae3 Compare April 29, 2024 19:19
@erights erights changed the base branch from master to markm-better-pattern-types April 29, 2024 19:20
@erights erights changed the title refactor(patterns): improve types. Prepare for compression refactor(patterns): Prepare for compression Apr 29, 2024
Base automatically changed from markm-better-pattern-types to master April 29, 2024 20:18
erights added a commit that referenced this pull request Apr 29, 2024
closes: #XXXX
refs: #2248 #1584 Agoric/agoric-sdk#6432

## Description

Pure refactor. Changes only static info. Mostly more consistent and more
readable use of `@import`.

One case made less readable: Remove newlines within a large `@import`
directive. The reason is that
`yarn lerna run build:types` chokes on those newlines. TODO minimal
repro + report issue.

Extracted from other PRs #1584 #2248 which are now staged on this one.
But this should be a reviewable and mergeable improvement regardless of
whether we move forward on the others.

### Security Considerations

none
### Scaling Considerations

none
### Documentation Considerations

none
### Testing Considerations

none
### Compatibility Considerations

none
### Upgrade Considerations
none

- ~[ ] Includes `*BREAKING*:` in the commit message with migration
instructions for any breaking change.~
- ~[ ] Updates `NEWS.md` for user-facing changes.~
@erights erights force-pushed the markm-prepare-for-extended-matchers branch 3 times, most recently from e3cfbad to d25cfad Compare May 2, 2024 23:18
@erights erights force-pushed the markm-prepare-for-extended-matchers branch 5 times, most recently from aa85135 to b619239 Compare May 9, 2024 00:09
@erights erights force-pushed the markm-prepare-for-extended-matchers branch from 964d1ac to 4c7ac33 Compare May 24, 2024 03:41
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

1 participant