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

v1.0.0 merge #18

Merged
merged 6 commits into from
Jun 12, 2024
Merged

v1.0.0 merge #18

merged 6 commits into from
Jun 12, 2024

Conversation

roddymunro
Copy link
Member

No description provided.

* Add ArgumentParser dependency

* Rename SwiftPolyglotCore struct

* Add RuntimeError

* Rename SwiftPolyglot struct, add ParsableCommand adoption and add RuntimeError usage

* Parse arguments and flag using ArgumentParser and adjust SwiftPolyglotCore initializer's parameters

* Update README

* Rename property

* Format

* Fix command name in help's message
* Set minimum macOS version to version 10.15 (Catalina)

* Add MissingTranslation struct

* Add concurrency to core functionality

* Adopt AsyncParsableCommand protocol to provide an asynchronous entry point

* Add XCTest extension for testing async throwing expressions

* Add concurrency to tests
@pereBohigas
Copy link
Contributor

I fixed almost all SwiftFormat issues in #19, you can take a look at it

pereBohigas and others added 2 commits May 29, 2024 18:25
* Remove trailing commas

* Fix indentation

* Move inline try to start of expression

* Remove trailing white spaces

* Use opaque generic parameters instead of generic parameters with constraints

* Replace consecutive blank lines with a single blank line
@roddymunro
Copy link
Member Author

roddymunro commented May 29, 2024

Weird that this passed on #20 ! Taking a look

Edit: Fixed :)

@pereBohigas
Copy link
Contributor

I modified the custom methods on XCTest for asserting on async throwing expressions to avoid disabling the hoistAwait rule of SwiftFormat in #22, you can take a look at it

* Add Equatable adoption for custom error

* Improve custom method for asserting on asynchronous expressions which should run successfully without throwing an error

* Improve custom method for asserting on asynchronous expressions which should throw an error

* Reenable hoistAwait SwiftFormat rule
@roddymunro
Copy link
Member Author

@pereBohigas I'll be looking to merge this as soon as next week and release version 1.0!

@roddymunro roddymunro merged commit 2d5751c into main Jun 12, 2024
2 checks passed
@roddymunro roddymunro deleted the v1 branch June 12, 2024 23:29
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