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

Version 1.2.0 #16

Merged
merged 13 commits into from
Mar 8, 2020
Merged

Version 1.2.0 #16

merged 13 commits into from
Mar 8, 2020

Conversation

originalfoo
Copy link
Member

@originalfoo originalfoo commented Mar 5, 2020

Major update:

Fixes #18 - log should show num occurrences of assembly
Fixes #14 - struct for mod + assembly info
Fixes #13 - refactoring folders + classes
Fixes #12 - log MD5 of assemblies
Fixes #11 - indicate if assembly is loaded, indicate if mod is enabled
Fixes #10 - show detailed results in mod options screen
Fixes #9 - scan mod folder if it's PluginInfo doesn't list the assembly

Major update
@originalfoo originalfoo added the enhancement New feature or request label Mar 5, 2020
@originalfoo originalfoo added this to the 1.2.0 milestone Mar 5, 2020
@originalfoo originalfoo self-assigned this Mar 5, 2020
@krzychu124
Copy link
Member

I'll test it later today 😉 I need 😴 💤

@dymanoid
Copy link

dymanoid commented Mar 6, 2020

As a general note regarding your git commits. Consider reading this great blog post about the git commit messages. I'd even recommend to publish a link to this in your contribution guide. The blog post explains how to make your git history readable and clean.

  • Limit the subject line to 50 characters
  • Use the imperative mood in the subject line (Simplify, not Simplified / Simplifying / Simplification)
  • Capitalize the subject line
  • Do not end the subject line with a period
  • Use the body to explain what and why vs. how (if there is something the developers need to know besides the subject line)
  • Separate subject from body with a blank line (if there is a body)
  • Wrap the body at 72 characters (if there is a body)

In `Release` builds, constant TRACE is not wanted. Replace it with RELEASE.

References do not specify assembly version, public key, etc. Add that detail.

The post-build script contains hard-coded paths and is somewhat opaque as to
how the local C:SL folders are structured. Make use of macros and environment
variables to generalise the script, and echo folder paths to build console as
visual confirmation that the correct paths are being used.
`MangedDLLPath` should be `ManagedDllPath`.
ModAssembly is a class, not a struct.

The Structs folder is no longer required.
@originalfoo originalfoo merged commit 8d3e7d6 into master Mar 8, 2020
@originalfoo originalfoo deleted the v1.2.0 branch March 8, 2020 12:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
3 participants