CSV file encoding not explicitly set to UTF-8

Open Beginner friendly
#63 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
csharp
Domain
data

Research direction

Open FileProcessor.cs at line 25 and inspect how the StreamWriter is constructed. Make the encoding explicit as UTF-8, then verify that generated CSV output remains UTF-8 encoded and that the existing project checks still pass.

Written by the indexing model from the issue text.

Description

enhancement

Description

\FileProcessor.cs\ uses
ew StreamWriter(filePath)\ which defaults to UTF-8 without BOM. However, the OneRoster 1.1 Best Practice Guide (section 4.1) requires:

'The CSV files must be UTF-8 encoded [RFC3629].'

While the default StreamWriter behavior produces UTF-8, being explicit avoids ambiguity across platforms.

File to fix

\FileProcessor.cs\ line 25 — change to:

\\csharp
using var writer = new StreamWriter(filePath, false, System.Text.Encoding.UTF8);
\\

Impact

Low — current output is already UTF-8, but explicit encoding removes any ambiguity.

Dominant language
C#
Stars
4
Forks
1
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bergerb/OneRosterSampleDataGenerator

All issues in bergerb/OneRosterSampleDataGenerator

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.