UiPath Custom Activity dependency output argument not using correct type


I have been building a custom dependency to try and port an equivalent for some features of the git bash software as UiPath activities, so they can be used in UiPath without needing to use the command prompt, or requiring any external software to be installed (whether it be GIT bash, or an alternative desktop GIT software)

The issue I am facing is that the activity code (written in C#) shows the output of the activity as being the correct type and allows me to demonstrate this. (I have added code to go through the output list to log the author and author date, to make sure that the commit type variable does support the attributes)

However when being run in studio I can see the console messages as traces, showing that the attributes do exist for the type of variable, however I don’t seem to be able to see this when trying to use the variable in UiPath, I am only able to see the commit hash.

Any ideas what may be causing this would be much appreciated.

Hello @George_Eden!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

  5. Meet us and our users on our Community Slack and ask your question there.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly