Project Description

Write a plugin for the most common IDEs capable of parsing a supportconfig file, enable the folding of its section and retrieving an outline of the current file; giving context infos when navigating through the file (which file and which sections are being navigated) would be a plus.

Goal for this Hackweek

  • Write the plugin for VS Code

UPDATE: goal achieved, here is the extension!

Goal for the upcoming Hackweeks

  • Evaluate the porting for IntelliJ IDEA and Eclipse
  • Evaluate if Notepad++ is capable of giving the desired features
  • Evaluate and eventually implement a SCA plugin capable of writing on the fly a web page having a pseudo-IDE nested giving the desired features

Resources

VS Code extension

VS Code Grammar

TextMate Lang Tutorial

TextMate Lang Specs

SWMF example plugin

Looking for hackers with the skills:

supportconfig ide

This project is part of:

Hack Week 22

Activity

  • almost 2 years ago: GKnudi started this project.
  • almost 2 years ago: paolodepa added keyword "supportconfig" to this project.
  • almost 2 years ago: paolodepa added keyword "ide" to this project.
  • almost 2 years ago: paolodepa originated this project.

  • Comments

    • paolodepa
      almost 2 years ago by paolodepa | Reply

      Tracking my progress (if any add-emoji ) here: https://github.com/paolo-depa/suse-supportconfig-parser

      Feel free to contribute

    Similar Projects

    suse-rancher-supportconfig by eminguez

    Description

    SUSE's supportconfig support tool collects data from the SUSE Operating system. Rancher's rancher2_logs_collector.sh support tool does the same for RKE2/K3s.

    Wouldn't be nice to have a way to run both and collect all data for SUSE based RKE2/K3s clusters? Wouldn't be even better with a fancy TUI tool like bubbletea?

    Ideally the output should be an html page where you can see the logs/data directly from the browser.

    Goals

    • Familiarize myself with both supportconfig and rancher2_logs_collector.sh tools
    • Refresh my golang knowledge
    • Have something that works at the end of the hackweek ("works" may vary add-emoji )
    • Be better in naming things

    Resources

    All links provided above as well as huh