Help add features and make it event better!

The success of Glass.Mapper has been down to the community who have been contributing awesome new features, identifying and fixing bugs. So if you have a great new idea or have noticed something not working as expected then please let us know.


Contributing a feature:

Steps to getting started:

  1. First you need to
  2. Next pull down your fork to your local machine.
  3. Make sure that any changes you make are made on the develop branch. For the Glass.Mapper project we use the branching strategy described Vincent Driessen. We would recommend that you setup Git Flow to help you work with this branching strategy but it isn't necessary.
  4. Make your changes in the development branch.
  5. Push your changes back to your Github.
  6. Send us a pull request detailing your changes.
We may need to contact you to ask you questions about your pull request and we might want to talk to you in person to clarify anything we don't understand.

Telling us about a problem

If you find a problem with Glass.Mapper then please let us know by following these simple steps:

  1. Open an issue on Github
  2. When logging and issue please try to include:
    • Details of the issues
    • Steps you took to cause the issue
    • Stack trace if possible
    • A copy of the model you were trying to map
    • A snippet of the code that you were using to do the mapping
    • The Sitecore field types you are using.

We will then assess the issue and contact you for more information if needed. If the issue is critical, often we will release a hotfix very quickly, (our record has been 20 minutes).

Glass.Mapper.Sc is an open source project and the contributors give their time freely to support the project. We therefore cannot guarantee when and issue will be fixed. If your issue is urgent then please contact our paid for Support.