Skip to content

Conversation

@djbe
Copy link
Member

@djbe djbe commented Feb 10, 2019

Fixes #365.

It's been a while since I did anything beyond very basic Ruby stuff, so don't shoot me 😅 Also, naming things is hard...

Note: this is based on #598, which should be merged first.

@djbe djbe added this to the 6.2.0 milestone Feb 10, 2019
@djbe djbe changed the title Feature/compile output with config Tests: compile output with config files Feb 10, 2019
@djbe djbe changed the title Tests: compile output with config files Tests: compile output using config files Feb 10, 2019
@SwiftGen-Eve
Copy link

SwiftGen-Eve commented Feb 10, 2019

1 Warning
⚠️ Big PR

Hey 👋 I'm Eve, the friendly bot watching over SwiftGen 🤖

Thanks a lot for your contribution!


Seems like everything is in order 👍 You did a good job here! 🤝

Generated by 🚫 Danger

@djbe djbe force-pushed the feature/compile-output-with-config branch 2 times, most recently from 2afc42f to 7f5a30b Compare February 10, 2019 16:54
@djbe djbe force-pushed the feature/compile-output-with-config branch from 7f5a30b to c26ac3d Compare February 10, 2019 17:45
@djbe djbe changed the base branch from feature/move-generated-output to develop February 10, 2019 17:46
@djbe djbe merged commit f14727f into develop Feb 10, 2019
@djbe djbe deleted the feature/compile-output-with-config branch February 10, 2019 20:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants