GOLAND BUILD TAGS UPDATE

When you notice anything, please be sure to submit it to our issue tracker. Please help us test it more thoroughly to find and get fixed all the important issues before the release. Once again, let us remind you that weвЂ™re getting close to the release date. The Run Configuration dialog now has an option to automatically include the tags specified in Settings | Go | Vendoring & Build Tags into the command line:ДЇor the complete list of changes in the build, please check out the release notes. Now, if the tests youвЂ™re running have build tags that are not listed in Settings | Go | Vendoring & Build Tags, the IDE will automatically include the tags in the command line: Multiple tags can be supported with tag1tag2tag3, where an AND matching condition ( tag1 & tag2 & tag3 ) is used for selection. Running tests with build tags got easier. This proposal is to extend filename build constraints to include build tags with a tag pattern in the filename suffix, before any GOOS and/or GOARCH patterns. Now the IDE also offers Remove directory from current project to quickly remove the content root from the project: Note, to make it work, you have to use a Go distributive built from the sources.Д®arlier we added Add directory to the current project to the context menu of the Project tool window so you could quickly add a content root to the project. Now if you use Run with Coverage on a folder that has several packages, the IDE properly collects and displays the coverage data for all packages: The upcoming Go 1.10 is going to support running tests with coverage from multiple packages. The Call Hierarchy introduced earlier now has a button that toggles the mode in which it additionally shows the calls on interfaces: To enable it, go to Settings | Go, and check Show documentation in parameter info:

Now you can see the documentation on function parameters as a part of the Param Info popup:

GOLAND BUILD TAGS UPDATE

At the same time, the update includes several new features. The published update comes with plenty of bugfixes. Since weвЂ™re approaching the release date (roughly early December), we are now paying more attention to fixing important issues and the overall stability of the IDE. ItвЂ™s similar to how xml package works, but of course a lot simpler.WeвЂ™ve just published a fresh GoLand EAP build. Behind the scene, it will fill the struct with appropriate data based on the tags provided. What I wanted to achieve was an abstract parser that recieves a slice of byte, a struct and returns error if any. Structs in Golang represent one of the most common variable types and used practically everywhere, from dealing with configuration options to marshaling of JSON or XML documents using encoding/json or encoding/xml packages. HTML parsing packages usually build their own conventions on top of DOM nodes to make traversing through them easier. I need a more abstract approach.ДЇortunately, HTML parsing at its core is just returning DOM nodes based on a valid CSS selector. The main problem is that each parser implementation provides its own structs and ways to work with HTML. It all started with a simple idea about an interface to describe how a HTML parser should work without it being tied to the underneath parser logic. I will assume that if you read this you probably have used struct tags before, and have a basic understanding about them. While doing my side project, I implemented a package to parse HTML content similar to how the native XML parser works. ItвЂ™s similar to how HTML and CSS are separated by class names. With tags, I can separate the data structure from the meta data used by other parties. As a total beginner to Golang I find struct tags a very interesting idea.

Goland build tags