Finish formatting
- Dominant language
- Java
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Update UddlFormatter.xtend so that it properly formats everything.
To see how the formatter works, install everything per the setup instructions. Then start a second Eclipse.
In that second Eclipse,
1. create a new blank project (File -> New -> Project or File->New->Other->General->Project) and click Next.
1. Give it a name and click Finish.
1. copy the following file from the first Eclipse to the new project:
/com.epistimis.uddl.tests/src/com/epistimis/uddl/tests/UDDL_SDM_Min.uddl
1. Open the UDDL file in the new project.
1. Select the edit window, and use Cmd-Shift-F on Mac or Alt-Shift-F on Windows to format the file.
## Modifying the code
The code that formats the UDDL file can be found in
/com.epistimis.uddl/src/com/epistimis/uddl/formatting2/UddlFormatter.xtend
It already contains a lot of work - but it is not yet complete. Nor is the sample UDDL file. Your task is to use what you see as an example and extend the code to properly format
* Everything you see in the existing UDDL file;
* One or more larger UDDL files that contains at least 3 of each of the things described in the Uddl.xtext file.
Note that the example UDDL file you see is already partially formatted. That won't always be the case. You should create sample files that take worst case formatted files (there are at least 2 worst cases - at opposite ends of the spectrum) and make sure your formatting works on them as well. You can create those worst case formatted files starting from the sample file if you want.
Contributor guide
Research direction
Start with /com.epistimis.uddl/src/com/epistimis/uddl/formatting2/UddlFormatter.xtend and compare its existing rules with Uddl.xtext and UDDL_SDM_Min.uddl. Follow the setup instructions to format the sample in Eclipse, then create larger and worst-case-formatted UDDL samples. Done means the existing sample and larger files containing at least three of each described item format properly.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100